Compiling stuff with g++ on SVr4

Thread View: comp.unix.sysv386

1 messages

[T] Back to Threads [V] Tree View [G] Group Articles

1 total messages Started by Ronald F. Guilmette Mon, 21 Dec 1992 09:31

#10491

Author: Ronald F. Guilmette
Date: Mon, 21 Dec 1992 09:31

31 lines
1769 bytes

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

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads