dag@per2.UUCP (Daniel A. Glasser) (12/09/89)
I've recently FTP'ed the binaries for GNU-C 1.35 and the 1.36 executable
zoo from the Terminator archive and have attempted to use it for building
NetHack 3.0 pl 3 according to the makefile and other docs (makefile.tos
and install.dos) and have come up with a few problems: (The notation [*]
is used when a given number (1=[*], 2=[**], etc.) of bombs accompanied the
failure)
The compiler does not seem to like "#include <sys/whatever>"
I had to change these all to "#include <sys\whatever>".
Makedefs.prg does not work correctly -- it appears to be a
problem with the printf function in the gcc library on
terminator which makes %d (in the 16 bit library) display
(and consume from the stack) long values. Also, the
freopen seems always to fail [**]. I hacked around this problem
and then came to problem # 3 --
The make dies about 2/3 of the way through do to file-not-found's
from #include directives. Restarting the make with appropriate
changes to the makefile got me through to having all of the
files compiled. Then
Gld died (***) when invoked from the makefile. Some of this seems to
be because of too many arguments on the command line. I searched
the sources for an older version of gld and discovered that I
could create a file containing the names of objects to be
linked and use "@linkfile" on the gld command line to use it.
Once I finally got a nethack.ttp file out of all of this (after several
days of hair pulling and head banging), attempting to run that
file didn't work (**).
Has anybody put together a configuration of GCC running on an ST that
works?
My set-up is a Mega ST-4 with 68 meg of hard disk, TOS 1.2 and a Mono-monitor.
I have FOLDR400.PRG in my auto directory, and I run gnu-make from under
a modified MWC shell.
I've read of an improved and fixed library available on "bammi's machine",
but my FTP site has never heard of it by the name I have for it, and no
number was given for that site. Someone should put the updated libraries
on terminator with the other ST specific GNU stuff. The "\" vs "/" stuff
seems to be a difference in CPP versions. I can find no documentation on
gld, gas, or the GNU C library. I have TeX/LaTeX and texinfo.tex, a laser
printer and the associated DVI-to-laser program so I can print out any
documentation from the .texinfo sources, if they exist.
Can anyone give me pointers, descriptions, how-to's or other advice?
I've got TOS 1.4 on order, and will install it sometime in the next two
weeks (I hope).
I can be reached directly via uucp mail at uwvax!per2!dag. uusend does
not work to this site, so please don't try it. I have FTP access through
a guest account on a machine nearby.
Thanks in advance --
Daniel A. Glasser
--
_____________________________________________________________________________
Daniel A. Glasser One of those things that goes
uwvax!per2!dag "BUMP!!!(ouch)" in the night.
---Persoft, Inc.---------465 Science Drive-------Madison, WI 53711-----------bobw@hpsad.HP.COM (Bob Waltenspiel) (12/13/89)
>Has anybody put together a configuration of GCC running on an ST that >works? I'm attempting to setup a system to use GCC as well. You seem to be a bit further than I, so I have no answers to your questions. I am posting this to show that there are people out here trying to use the GNU stuff and having trouble. Those in the know, please respond to this basenote. My specific questions is below. >My set-up is a Mega ST-4 with 68 meg of hard disk, TOS 1.2 and a Mono-monitor. >I have FOLDR400.PRG in my auto directory, and I run gnu-make from under >a modified MWC shell. I have a 520ST w/2.5M and color screen, ICD Host Adaptor with 44M of disc space. I'm using the Gulam shell. I've been attempting to get gdb going but have not been able to get it to allow me to debug at the source level. I have to link in a second step after compiling because I don't have gnugdb.olb. I don't want to get all the the gnu sources to compile my own copy. Could someone please send me one? A question about when using gdb. First what I'm doing. >cc -c -gg hello.c <gives me a hello.o file> >sym-ld -r -o hello.sym c:\bin\gnu\lib\crt0.o <gives me a hello.sym file> >cc hello.o -o hello.ttp <gives me a hello.ttp file (the executable, although I haven't tried to execute it by itself)> >gdb <start gdb> (gdb) sym hello.sym <something about loading sym table...done> (gdb) exec hello.ttp (gdb) run <starts hello.ttp giving what looks like an address and some signal info> (gdb) list Listing source requires symbols. <I thought I have the symbols with the sym command?> (gdb) step <more address info> What do I need to do to have it step through and show me the source code? I want to use gdb at the highest level, after all, I'm just learning this stuff. >Can anyone give me pointers, descriptions, how-to's or other advice? Yes, please do this. > Daniel A. Glasser -Bob ----------------------------------- ----------------------------------------- | Bob Waltenspiel | e-mail: bobw@hpsad (hplabs!hpsad!..) | | ATE Software Team | Telnet: 794-3091 | | HP Signal Analysis Division | AT&T: (707) 794-3091 | | 1212 Valley House Dr. | HPDesk: Bob WALTENSPIEL/HP5300/A0 | | Rohnert Park, CA 94928-4999 | HP Mailstop: 1UR-M | ----------------------------------- ----------------------------------------- Although Pooh's head was stuffed with fluff, he was a cheerful fellow.