OK, I checked to see if I've got any flavor of libstdc++.so in
/usr/lib and, not too hip with scripts yet, so I did:
# ls -l /usr/lib |grep libstdc++
-r-xr-xr-x 1 root root 424201 Mar 23 17:39 libstdc++-3-libc6.1-2-2.10.0.so
lrwxrwxrwx 1 root root 33 Apr 28 17:15 libstdc++-libc6.1-1.so.2 ->
/usr/lib/libstdc++-libc6.1-2.so.3
lrwxrwxrwx 1 root root 31 Apr 28 16:32 libstdc++-libc6.1-2.so.3 ->
libstdc++-3-libc6.1-2-2.10.0.so
lrwxrwxrwx 1 root root 31 Apr 28 16:32 libstdc++.so.2.9 ->
libstdc++-3-libc6.1-2-2.10.0.so
Is it possible the second of the four lines above
libstdc++-libc6.1-1.so.2 should be a symlink to
libstdc++-3-libc6.1-2-2.10.0.so like the other three?
Could it be I need to change one symlink?
What about the line which says:
checking whether the C compiler (gcc ) is a cross-compiler... no
Does this tell you anything?
* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [000807 21:46]:
>
>
> On Mon, 7 Aug 2000, Richard Spencer wrote:
>
> > OK, I thought we had fixed this thing, but when I tried (as root) to
> > install a console game black_jack-0.1.tar.gz I got the following:
> >
> > # ./configure
<snip>
> > checking whether the C compiler (gcc ) works... yes
> > checking whether we are using GNU C... yes
> > checking whether the C compiler (gcc ) is a cross-compiler... no
> > checking whether gcc accepts -g... yes
> > checking for c++... no
> > checking for g++... g++
> > checking whether the C++ compiler (g++ ) works... no
> > configure: error: installation or configuration problem: C++ compiler
> > cannot create executables.
> >
> > I suppose it's a source tarball -- I don't recall :-|
> > I'll be sure to make that distinction in the future.
> >
> the c compiler works. that means you have basically the entire gnu tool
> chain. The only thing that might be missing/misplaced is libg++
> libstdc++. I really thought they were part of gcc-2.95.1 - hang on, let
> me check. libstdc++ is part of gcc. libg++ seems to have withered
> away. my only c++ program, hw.C:
>
> #include <iostream.h>
> int main(void){ cout<<"Hello World"<<endl; }
>
> Script started on Mon Aug 7 18:01:05 2000
> witsend:~$ g++ -o hwC hw.C
> witsend:~$ ./hwC
> Hello World
> witsend:~$ ldd hwC
> libstdc++-libc6.1-2.so.3 => /usr/lib/libstdc++-libc6.1-2.so.3
> (0x4001a000)
> libm.so.6 => /lib/libm.so.6 (0x4005f000)
> libc.so.6 => /lib/libc.so.6 (0x4007b000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
> witsend:~$ exit
> exit
>
> Script done on Mon Aug 7 18:02:17 2000
>
> maybe if you run a test like that you can see what is missing. That is
> approximately what your average ./configure does to test a compiler.
>
> sometimes ./configure puts interesting comments in config.log.
>
> maybe libstdc++ wants a newer glibc than you have?
>
> ldd /usr/lib/libstdc++.so
>
> should show that. I hope not.
>
> Lawson
--
Running Redhat 6.0 with some upgraded packages.
Richard Spencer "Why Not" is a slogan
Sao Paulo, Brazil for an interesting life.
[EMAIL PROTECTED] -- Mason Cooley
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
