Re: [Slightly OT] Compilers for Angband

On Thu, 06 Oct 2005 19:57:52 GMT, David Howdon
<"davidhowdon[nospam]"@[donotspamme]yahoo.com> wrote:

(snip quoteback)
>I seem to be having exactly the same problem when trying to compile so
>if any memories of what you did come back to you I would be grateful.

Hi David,

Going from memory, these are the steps as I remember them.

1. Follow steps on Thangorodrim (but see below).
2. Attempt to compile and make.
3. Compiler finished okay; linker reported error code 1.
4. Wasted lots of time looking for error codes in lcc-win32 help files
or web sites for error code 1.
5. Finally, found a file named Angband.err in the map src\lcc. Opened
this to find a reference to main_win.c. I believe that a reference to a
line number or to a name (of a called sub) was included as well, though
an underscore was prefixed to the name.
6. Opened main_win.c in lcc-win32's edit window. Tried to find the
offending code. Failed.
7. Re-attempted the make. I can't recall if I made some bogus change
first to force recompile of main-win.c as well. Now, the error was
reported with a descriptive text in the output window. Something about a
missing library.
8. Clicked, right-clicked or doubleclicked (can't recall) on the error,
to get to the offending line. Either at that moment, or after I clicked,
right-clicked or doubleclicked somewhere in that line, a request popped
up if I wanted lcc-win32 to add the missing library. Replied "yes".
9. Attempt to compile and make. No errors reported.
10. Play.


>Another question is that the instructions on Thangorodrim say "Add all
>files from birth.c to load.c to the project, then add the "main-win.c"
>file with the "Add new file..." option and finally the files from
>melee1.c to z-virt.c." What this seems to be intended to do is to
>install all of the *.c files except for the main-*.c files relating to
>other operating systems.
>However following these instructions literally means that the files
>l-*.c are not included. Are they not supposed to be?

They should be included. Jeff Greene pointed that out in an earlier
message in this thread. Look it up - it has some other good information
as well, that you really shouldn't miss if you intend to tweak the code.

Best, Hugo
--
Your sig line (k) was stolen! (more)
There is a puff of smoke!

(Remove NO and SPAM to get my e-mail address)
.

Relevant Pages

  • trouble compiling some ports
    ... of course with the ports up to date. ... won't compile with multipal jobs. ... stops with an error code 1 while still saying that everything is ok. ... Object directory not changed from original ...
    (freebsd-questions)
  • Compiling X11R6.8.2 or 6.8.1 or 6.8.0
    ... I am trying to install X11R6.8.2 on Solaris 8, so I can install Xvfb, so ... the sunmanagers search...Does it compile with gcc? ... *** Error code 2 ... make: Fatal error: Command failed for target `Pci.o' ...
    (SunManagers)
  • Re: SAPI & .net
    ... When you compile you have the error code you give. ... returned because it can't find the CLSID in your Registry Settings. ... The Guid is the guid ...
    (microsoft.public.windowsce.platbuilder)
  • RE: I must be doing something wrong!
    ... *** Error code 1 ... Can you just catch the tree at a bad time when it will not compile? ... >port tells me 'it will not compile so dont even bother trying'. ...
    (freebsd-questions)
  • Re: Passing C++ array to Fortran function?
    ... illegal equivalences to compile. ... but I recall the discussion of the ... two elements being equal vs all of the elements being zero. ...
    (comp.lang.fortran)