home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.programmer
- Path: sparky!uunet!news.claremont.edu!nntp-server.caltech.edu!news
- From: ernest@pundit.cithep.caltech.edu (Ernest Prabhakar)
- Subject: Re: GCC-2.2.2, 3.0PR2
- Message-ID: <1992Sep8.174759.20269@cco.caltech.edu>
- Sender: news@cco.caltech.edu
- Nntp-Posting-Host: pundit.cithep.caltech.edu
- Reply-To: ernest@pundit.cithep.caltech.edu (Ernest Prabhakar)
- Organization: California Institute of Technology, Pasadena
- References: <Bu8A6F.Iz1@world.std.com>
- Date: Tue, 8 Sep 1992 17:47:59 GMT
- Lines: 20
-
- In article <Bu8A6F.Iz1@world.std.com> gsk@world.std.com (Geoffrey S Knauth)
- writes:
- > Has anyone successfully compiled GCC-2.2.2 under NeXTstep 3.0PR2?
- > rtl.c won't compile, because __extension__ is not defined away
- > to nothingness. Before I start impurifying GCC sources, I thought
- > I'd ask if anyone else has been down this road.
- >
- What I did was get the GCC 2.1 binaries from the archives, and compiled gcc
- 2.2.2 with that. It turned out to work just fine. I also hacked cccp.c to
- follow NeXT's bizzare header file format, and that also (as far as I've
- checked, which isn't too far) works fine. Once I did that, libg++ also
- compiled fine. So, it's tricky but not impossible.
- - Ernie P.
- P.S. Yes, I'm also using PR2
- --
- Ernest N. Prabhakar Caltech High Energy Physics
- Member, League for Programming Freedom (league@prep.ai.mit.edu)
- CaJUN President NeXTMail:ernest@pundit.cithep.caltech.edu
- "...and ourselves, your servants for Jesus sake." - II Cor 4:5b
- #import <std/disclaimer.h>
-