Re: c++ problems
On Tue, May 15, 2001 at 07:55:10AM +1000, Craig Sanders wrote:
> any idea what could cause this? is it a bug in the g++-2.95 package,
> perhaps not setting the library path properly or something?
>
>
> during the ./configure stage of compiling a new version of galeon, i
> get:
>
> ...
> checking for c++... c++
> checking whether the C++ compiler (c++ ) works... no
> configure: error: installation or configuration problem: C++ compiler cannot
> create executables.
> make: *** [configure-stamp] Error 1
>
>
> # tail config.log
> configure:1409: checking whether the C++ compiler (c++ ) works
> configure:1425: c++ -o conftest conftest.C 1>&5
> cpp: -lang-c++: linker input file unused since linking not done
> c++: installation problem, cannot exec `cc1plus': No such file or directory
> configure: failed program was:
>
> #line 1420 "configure"
> #include "confdefs.h"
>
> int main(){return(0);}
>
>
>
> there's a problem there already but if i set the PATH so that it can
> find cc1plus by PATH="$PATH:/usr/lib/gcc-lib/i386-linux/2.95.4/", the
> tail of config.log changes to:
>
> # tail config.log
> configure:1409: checking whether the C++ compiler (c++ ) works
> configure:1425: c++ -o conftest conftest.C 1>&5
> cpp: -lang-c++: linker input file unused since linking not done
> ld: cannot open crtbegin.o: No such file or directory
> configure: failed program was:
>
> #line 1420 "configure"
> #include "confdefs.h"
>
> int main(){return(0);}
>
> i have the following gcc & g++ packages installed (these are the latest
> versions available in unstable):
>
> # dlocate -l gcc\\\|g++ | grep "^ii"
> ii g++ 2.95.3-7 The GNU C++ compiler.
> ii g++-2.95 2.95.4-0.01050 The GNU C++ compiler.
> ii gcc 2.95.3-7 The GNU C compiler.
> ii gcc-2.95 2.95.4-0.01050 The GNU C compiler.
> ii gcc-3.0 3.0-0pre010427 The GNU C compiler.
> ii gcc-3.0-base 3.0-0pre010427 The GNU compiler collection (base package).
> ii libg++2.8.1.3- 2.95.4-0.01050 The GNU C++ extension library - runtime vers
> ii libgcc0 3.0-0pre010427 Shared libgcc.
>
If galeon makes use of libtool, I believe I know the problem and a
possible solution.
libstdc++3-dev installs /usr/lib/libstdc++.la with information specific
to building for v3. It will cause your package to try to use both 2.95.x
and 3.x. Bad mixup, Ben C is aware of this and I believe he plans to
rectify it.
Simple solution, remove/move /usr/lib/lib{supc++,stdc++}.la if your are
building a libtool using c++ package intended for gcc 2.95.x and you
have libstdc++3-dev installed.
--
Gordon Sadler
Reply to: