* [EMAIL PROTECTED] <[EMAIL PROTECTED]> [000807 23:56]:
> 
> 
> On Mon, 7 Aug 2000, Richard Spencer wrote:
> 
> > 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?
> >
> Maybe, but I don't think that is the one.  It is all right to have one
> library symlink point to another, as long as it resolves to a real
> library eventually.
> 
> > What about the line which says:
> > checking whether the C compiler (gcc  ) is a cross-compiler... no
> > Does this tell you anything?
> >
> Not a thing.  gcc is configured to compile code to run on the same kind
> of system it runs on, not object code that will run on an ibm 390 or an
> atari or whatever, so it is not a cross-compiler.
> 
> libstdc++ version numbers just boggle me, the same as c++ does (why
> would you _want_ to overload a function?).  I tend to rely on ldd to
> figure out whether the libraries called for are present.
> 
> Why don't you compile a little sample C++ program (you are welcome to
> hw.C if you don't have anything better), see if you get any complaints
> from ld, see if ldd can resolve its library references.  See if it runs.

...compile a little program?
Do you want me to run something similar to what you ran?
I'll gladly do so, if I can figure out how :-)


> Depending on your MUA (mail user agent) you may need to fromdos files
> you pull out of the mail before trying to run/compile them:
> 
> tr -d "\r" <mailfile >linuxfile
> 
> slackware has a program fromdos to take care of that, but that is
> exactly what it does.
> 
> Also, do an ldd on the one libstdc++ that is a real file, and see if it
> is finding a libc version that is to its liking.
> 
# ldd /usr/lib/libstdc++-3-libc6.1-2-2.10.0.so
        libm.so.6 => /lib/libm.so.6 (0x4004e000)
        libc.so.6 => /lib/libc.so.6 (0x4006a000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)

> You will be able to tell from the ldd output if it wants something it's
> not finding, and we can go from there.
> 
> Lawson
> 
> 
> Half begun is well done.   - Benjamin Franklin Spooner
> 
> 
> 
> 
> ________________________________________________________________
> YOU'RE PAYING TOO MUCH FOR THE INTERNET!
> Juno now offers FREE Internet Access!
> Try it today - there's no risk!  For your FREE software, visit:
> http://dl.www.juno.com/get/tagj.
---cut here---

-- 
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

Reply via email to