home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.sysv386
- Path: sparky!uunet!spool.mu.edu!umn.edu!csus.edu!netcom.com!rfg
- From: rfg@netcom.com (Ronald F. Guilmette)
- Subject: Compiling stuff with g++ on SVr4
- Message-ID: <1992Dec21.093108.22105@netcom.com>
- Organization: Netcom - Online Communication Services (408 241-9760 guest)
- Date: Mon, 21 Dec 1992 09:31:08 GMT
- Lines: 31
-
- Some time ago, tannerrj@cnsvax (ROOT OF INSIGHT-- A 486 RUNNING ESIX V4.0.3A)
- wrote:
-
- > Anyone successfully built glib++ on Esix v4.03a? I have gcc 2.3.1
- > and it seems to work fine, but I get a tone of compilation
- > errors. If you have any knowledge of this problem, I can
- > mail you the error. Thanks.
-
-
- One big problem with compiling stuff (e.g. libg++) with the g++ compiler
- on any sort of UNIX system based on System V Release 4 is that the -g
- simply does not work (and you should not even try to use it). Using
- it will give you lots of weird assembler errors and/or linker errors
- (because the DWARF debugging-info output is bad).
-
- Why do these bugs (with g++ and -g on SVR4) still exist? Simple. Cygnus
- Support is either unwilling or unable to fix the interface from the g++
- front end to the DWARF generation routines (in dwarfout.c).
-
- Note that DWARF output for GNU C works flawlessly on SVR4 however.
-
- --
-
- // Ron ("Loose Cannon") Guilmette uucp: ...uunet!lupine!segfault!rfg
- //
- // "On the one hand I knew that programs could have a compelling
- // and deep logical beauty, on the other hand I was forced to
- // admit that most programs are presented in a way fit for
- // mechanical execution, but even if of any beauty at all,
- // totally unfit for human appreciation."
- // -- Edsger W. Dijkstra
-