herndon@milo.SRC.Honeywell.COM (William Herndon) (05/29/89)
No doubt this is a well worn set of questions but please indulge my
asking them one more time.
From what site can I obtain releases of gcc?
Is there any release that will compile using the 3b1 CC compiler?
If not, is there any release that will compile with a set of
diffs, and from where could the diffs be obtained?
Any and all help is appreciated.
-----------------------------------------------------------------------
William R. Herndon WHerndon@cim-vax.honeywell.com
herndon@src.honeywell.com
SCTC, Honeywell
2855 Anthony Ln. So. #130 (612) 782-7108
St. Anthony, Mn. 55418
The opinions expressed are solely those of the author. Any resemblance
to other opinions, either living or dead, is purely coincidental.alex@wolf.umbc.edu (Alex Crain) (05/31/89)
In article <22706@srcsip.UUCP>, herndon@milo.SRC.Honeywell.COM (William Herndon) writes: > No doubt this is a well worn set of questions but please indulge my > asking them one more time. Well worn, yes. but this comes up so often that its worth answering, me thinks. > From what site can I obtain releases of gcc? gcc is available from many places, although the most current is always prep.ai.mit.edu, in the /u2/emacs directory. That is the distribution site for all of the GNU software, much of which will run on the 3b1. > Is there any release that will compile using the 3b1 CC compiler? Not since 1.15, and you don't want to know about 1.15 :-) > If not, is there any release that will compile with a set of > diffs, and from where could the diffs be obtained? Its not diffs that you need, but a new preprocessor. The problem is that the stock cpp croaks on the number of #define's in the gcc code. The key is to either: a) get a cpp binary from somewhere. I mail them out periodically when asked, and one was posted to the net some time ago. ftp over to cheops.cis.ohio-state.edu and look through the archives. (Or maybe tut.cis.ohio-state.edu, I get those two confused) b) build the cpp that comes with the emacs distribution. c) Make a special config.h that only defines the symbols needed for cccp.c, and build a special cccp.c. You have to comment out the code in cccp.c that defines __STDC__ and __GNUC__, because the stock cc is neither ANSI nor GNU compatable. One you have this special cpp, replace /lib/cpp with it (temporarily) and compile gcc. Once you have a working gcc, you can compile future versions with that and you will (presumably) have no problems. At this point, there are fewer bugs in gcc then there are in cc. gcc also supports a -shlib switch (among many others) to compile with the shared libraries. I recommend the loader package that come over unix-pc.sources awhile back, it gives gcc all the functionality of shcc, with better code to boot! > Any and all help is appreciated. No sweat