🚀 go-pugleaf

In <jerry.753301158@kenya> jerry@tivoli.com (Jerry Frain) writes:

>We're strongly considering using g++ for C++ development on several
>platforms, but statically linking libg++ to each executable is going
>make our product rather bloated, I fear.

This means IMHO that you also should distribute the shared version og libg++;
and size of libg++.so & one executable will be bigger than the executable
linked to libg++.a.

If you plan on shipping more executables than your choice is OK.

>The above program (compiled with g++ and linked with my shared libg++)
>promptly core-dumped with a SIGSEGV in ostream::operator<<.  Line 612
>in iostream.cc, to be exact.  This is a bit distressing, since it is
>such a small, simple example.

The problem probably is that the global constructors (for cout at least)
are not called. You could fix that by placing this in a .sa library.

>I'm planning on continuing to try to build a working a shared libg++,
>but before I spend too much time on it, has anyone else attempted
>this?  Any ideas on how difficult this task might be?

Yes, somebody has attempted it for earlier versions of libg++.
(But don't know who :-()
I anticipate that it will not be difficult, but a lot of work.

Klamer
--
Klamer Schutte	 	    Tel: +31-53-892778  	Fax: +31-53-340045
Dept. of Electrical Engineering  --  University of Twente, The Netherlands
preferred: klamer@mi.el.utwente.nl              SMTP: klamer@[130.89.33.3]