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.
Regards
-richy.
--
Richard Kreckel
<[EMAIL PROTECTED]>
<http://wwwthep.physik.uni-mainz.de/~kreckel/>
