home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!elroy.jpl.nasa.gov!ames!haven.umd.edu!umd5!umd5.umd.edu!anderson
- From: anderson@sapir.cog.jhu.edu (Stephen Anderson)
- Newsgroups: comp.sys.next.software
- Subject: Gcc-2.3.2 and libg++2.3
- Message-ID: <ANDERSON.92Dec15130507@sapir.cog.jhu.edu>
- Date: 15 Dec 92 18:05:07 GMT
- Sender: news@umd5.umd.edu
- Distribution: comp
- Organization: Dept. of Cognitive Science, The Johns Hopkins University
- Lines: 16
-
- I've seen a couple of postings lately, suggesting that people have had
- trouble getting the current versions of gcc and libg++ for NeXT, and I
- just wanted to note that the versions presently on prep.ai.mit.edu
- (and various shadow archive sites) build virtually without problem
- under NS3.0. There is one NeXT include file that has a //-style
- comment where only /* */ style is acceptable; solutions to that were
- discussed a couple of weeks ago. Once you fix that one relatively
- trivial problem, building gcc-2.3.2 goes without a hitch. Just do
- "configure next" in the main directory, and go through the steps in
- the INSTALL file (you can even cut and paste the commands). Once you
- have gcc-2.3.2, building libg++ is exactly the same thing: "configure
- next" and then make, and everything chugs along without a problem.
- It's nice that the GNU configuration utilities are getting to be
- pretty good at figuring out where NeXT decided to put things in 3.0.
-
- --Steve Anderson
-