DragonFly bugs List (threaded) for 2004-07
Re: Unusual error message from gcc34 ?
Matthew Dillon wrote:
If everything is brought up to date (you cvsup, buildworld, installworld,
and make upgrade), and you then rebuild libtool, it should no longer fail
on crtbegin/end when you switch compilers...
Correct -- now it fails with missing C++ symbols when I switch compilers.
I know you have a few other things to do than worry about an experimental
compiler -- but if any solution comes to you spontaneously..... :o)
The problem is this: I compile/install libtool15 using gcc34, then go back
and compile 'aspell' using gcc2. This fails because the newly compiled
is *inappropriately* linked against /usr/lib/gcc34/libstdc++.so.6, even
thought I'm using gcc 2.95.
A similar error occurs if I compile libtool with gcc2 and aspell with gcc34.
All works well if both are compiled with the same compiler.
I believe this problem is inherent in libtool, not in DFly itself, but
I've been wrong before (according to my wife) so I thought I'd mention