home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.programmer
- Path: sparky!uunet!gatech!emory!wupost!usc!elroy.jpl.nasa.gov!ucla-cs!ucla-mic!agsm!iwelch
- From: iwelch@agsm.ucla.edu (Ivo Welch)
- Subject: Re: Problems using gcc 2.3.3
- Message-ID: <1993Jan1.110309.5899@mic.ucla.edu>
- Nntp-Posting-Host: risc.agsm.ucla.edu
- Organization: UCLA, Anderson Graduate School Of Management
- References: <PFKEB.92Dec30221114@kaon.SLAC.Stanford.EDU> <1992Dec31.154024.18427@fnbc.com>
- Date: 1 Jan 93 11:03:08 PST
- Lines: 14
-
- And, let's not forget that some of us need to debug programs, too. But NeXT
- gdb does not work with gcc 2.x.x, and NeXT has not forwarded its own changes
- to gdb to the FSF in their standard format; therefore, the FSF's new gdb
- version does not compile on NeXTs.
-
- So: either you can use NeXT's historic version of gcc with non-ANSI C++ syntax
- and no libg++, or you can use FSF version of gcc without NeXT Objective-C
- extensions and without a functional gdb.
-
- A pathetic state of affairs.
-
- /ivo welch
-
-
-