Hi Richard,
On Wed, Jun 14, 2000 at 09:31:43PM +0200, Richard B. Kreckel wrote:
> Hello,
>
> I had some quite painful experiences with newer libtools which link stuff
> together using gcc instead of c++. I know that was an issue on this list,
> I think I have read most of the pros and cons.
>
> Just let me add an arguments against the current situation which wasn't
> disussed so far AFAIK and forgive me if I have missed it on the archives.
>
> You configure a program, consisting of some libraries, some executables.
> One or more of the libraries use exceptions, though internally only. It
> is compiled with c++, linked with gcc. Now, if c++ and gcc don't match
> this may result in segmentation faults whenever an exception is thrown.
> Unfortunately there are many affected systems: Debian/Slink for instance
> comes with gcc 2.7.2.3 and c++ from egcs-2.91.60. It simply doesn't occur
> to normal users to export CC=egcc prior to configuring, which'ld give them
> the correct compiler and so I find myself answering fan mail...
>
> I really hope this is going to change some lucky day.
As a matter of fact, work is currently underway to add working C++
support to libtool. Currently supported compilers include GNU C++,
Sun C++, KAI C++ and Compaq C++. These same changes also make it
possible to add support for other languages besides C and C++, such as
Java! All of these changes are available in the libtool
multi-language CVS branch. Incidentally, the problems you point out
are taken care of by the features in this branch. These changes are
slated for libtool 1.5, but they won't be in Libtool 1.4.
Take a look at the libtool web site:
http://www.gnu.org/software/libtool/
for additional information on what is going in the libtool world.
-Ossama
--
Ossama Othman <[EMAIL PROTECTED]>
Distributed Object Computing Laboratory, Univ. of California at Irvine
1024D/F7A394A8 - 84ED AA0B 1203 99E4 1068 70E6 5EB7 5E71 F7A3 94A8
