Installing gcc on A/UX 1.1

Matthew T. Russotto russotto at eng.umd.edu
Wed Dec 6 08:46:10 AEST 1989


In article <1989Dec4.062116.3446 at servalan.uucp> rmtodd at servalan.UUCP (Richard Todd) writes:
>  The problem is that the source for gcc is too complex for Apple's C compiler
>to handle.  Believe it or not, the stock AT&T-derived CPP allocates space
>for handling defines from a *fixed size buffer* (32K, I believe), and if 
>your source code has more #defines than that, tough.  Rumour has it that 
>in SVR4 AT&T has finally learned about malloc(3) and fixed this piece of
>braindamage, but that's not much help to us now.
How about the C compiler in /usr/lib/big?  Is it able to handle gcc?
Not that it really matters of course-- given gcc binaries, gcc can be
used to compile itself, so this would just save a little download time.
Anyone else think it's ironic that Gnu's own philosophy prevents them
from stopping 'Evil Apple' from distributing their software...?
32K buffers?  Someone think that they are still using the 6502? Ack.
>--
>Richard Todd	rmtodd at uokmax.ecn.uoknor.edu  rmtodd at chinet.chi.il.us
>	rmtodd at servalan.uucp
>Motorola Skates On Intel's Head!


--
Matthew T. Russotto	russotto at eng.umd.edu	russotto at wam.umd.edu
][, ][+, ///, ///+, //e, //c, IIGS, //c+ --- Any questions?



More information about the Comp.unix.aux mailing list