Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!SFI.SANTAFE.EDU!scp
From: scp@SFI.SANTAFE.EDU ("Stephen C. Pope")
Newsgroups: gnu.g++.bug
Subject: Problem with libg++ and latest g++1.36.0-
Message-ID: <8910171448.AA03012@gila.santafe.edu>
Date: 17 Oct 89 14:48:39 GMT
References: <8910162054.AA14875@hope.lanl.gov>
Sender: news@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 27


One of the more significant problems with the all-in-one gcc
for compiling C and C++ shows up in SunOS 4.X systems, where
shared libraries are available.  gcc must use either the Sun-
supplied ld (which supports shared libraries), or gnu ld,
which does not support shared libraries, but is essential
for loading G++ code, due to the introduction of __main()
and the current style of static constructor/destructor
invocation.

I'm willing to accept that I can only link my g++ code
statically (I'm always debugging it anyway!), but that I should
have to accept static library loading for all my routine
C compilation work is definitely offensive.  I value gcc
highly for compiling all sorts of stuff - emacs, common tex,
X, etc, and the additional disk- and run time core-usage
is not a welcome bonus.  a GNU ld that supports shared
libraries would be a welcome event, of course, but...

As I'm also frequently suffling code between the AT&T and GNU
C++ compilers, the .c <-> .cc issue gets tiresome also;
I can fix CC to eat .cc suffixes, but not everyone has that luxury.


Stephen Pope
Santa Fe Institute
scp@sfi.santafe.edu