This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: Linux, libstdc++ and .cpp file extension
- To: "John Love-Jensen" <eljay at adobe dot com>
- Subject: Re: Linux, libstdc++ and .cpp file extension
- From: "Michael Mueller" <mmueller at signalnetware dot com>
- Date: Fri, 21 Sep 2001 22:33:26 -0400
- Cc: <gcc-help at gcc dot gnu dot org>
- References: <004501c142be$60e00c80$0601a8c0@LaptopME> <000201c142d4$8c0321c0$7801a8c0@mneljaypc> <000d01c142dc$c94894e0$0601a8c0@LaptopME> <016e01c142e5$68cc2d80$7801a8c0@mneljaypc>
Hello Eljay,
Please see responses below. I give an exhaustive answer to your
question:
What is the full path to libstdc++.so.3 ?
Thanks and best regards,
Michael
----- Original Message -----
From: "John Love-Jensen" <eljay@adobe.com>
To: "Michael Mueller" <mmueller@signalnetware.com>
Sent: Friday, September 21, 2001 5:36 PM
Subject: Re: Linux, libstdc++ and .cpp file extension
: Hi Michael,
:
: Just to clarify -- I'm using GCC 2.95.2 with (old and crusty)
: libstdc++.so.2.10 ... so I'm not suffering through the teething
pains of GCC
: 3.0.1 and the new 3.0 Standard C++ library. (Which, I believe, is
exactly
: the same as the 2.90 library blessed with a new version, in
conjunction with
: the new GCC release.)
:
: What does the "ldd a.out" or "ldd test" display?
This is from "ldd test". There is no a.out.
libstdc++.so.3 => /usr/lib/libstdc++.so.3 (0x40018000)
libm.so.6 => /lib/libm.so.6 (0x4007b000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x40097000)
libc.so.6 => /lib/libc.so.6 (0x4009f000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
:
: Note - I'm surprised that the LD_LIBRARY_PATH failed. :-( Side
note: the
: trailing '/' is superfluous and usually not explicitly given.
I tried again - hoping that I was making some careless mistakes. I
removed the libraries from /usr/lib and did
"LD_LIBRARY_PATH=/usr/local/lib" and ran "g++ -o test test.cc" and
ran "./test". I got the same error message as before.
:
: Is the code being compiled on one machine, and run on a different
machine?
Hmm, maybe I'd better reveal that larger picture and get your input.
The tests I am running are being compiled, linked, and run on a
single host - dev0. However, the reason for my interest in C++ is
that I have a daemon written in C that I want to enhance using C++.
I have a bunch of Finite State Machines in the daemon that talk to
each other and I thought that the base class and inheritance
concepts in C++ would work well to define the FSMs. Ultimately, I
will need to compile the daemon on dev0 and then run the daemon of
many other hosts.
:
: Sincerely,
: --Eljay
: Adobe
:
What is the full path to libstdc++.so.3 ?
# RedHat installed files
/usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/libstdc++.a
/usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/libstdc++.so
# I cp'd the next two files from /usr/local/lib after having mv'd
files as described in the next comment; I used "cp
/usr/local/lib/libstdc++.so.3* /usr/lib"
/usr/lib/libstdc++.so.3
/usr/lib/libstdc++.so.3.0.0
# I mv'd everything from /usr/lib/libstdc++* to /usr/lib/temp to
eliminate possible side-effects; previously I had "cp
/usr/local/lib/libstdc++* /usr/lib" which is why the .a .la and .so
files for libstdc++ exist here
/usr/lib/temp/libstdc++-2-libc6.1-1-2.9.0.a
/usr/lib/temp/libstdc++-2-libc6.1-1-2.9.0.so
/usr/lib/temp/libstdc++-libc6.1-1.a.2
/usr/lib/temp/libstdc++-libc6.1-1.so.2
/usr/lib/temp/libstdc++.a
/usr/lib/temp/libstdc++.la
/usr/lib/temp/libstdc++.so
/usr/lib/temp/libstdc++.so.2.7.2
/usr/lib/temp/libstdc++.so.2.7.2.8
/usr/lib/temp/libstdc++.so.2.8
/usr/lib/temp/libstdc++.so.2.8.0
/usr/lib/temp/libstdc++.so.2.9
/usr/lib/temp/libstdc++.so.2.9.dummy
/usr/lib/temp/libstdc++.so.3
/usr/lib/temp/libstdc++.so.3.0.0
# the make install for gcc 3.0 installed the next 5 files
/usr/local/lib/libstdc++.so
/usr/local/lib/libstdc++.so.3.0.0
/usr/local/lib/libstdc++.so.3
/usr/local/lib/libstdc++.a
/usr/local/lib/libstdc++.la
# RedHat installed files
/usr/i486-linux-libc5/lib/libstdc++.so.27.1.4
/usr/i486-linux-libc5/lib/libstdc++.so.27
# the next 5 files exist because I tried putting the libraries in
the development dir; no luck there; that was before I sent my first
email
/home/mike01/usr/src/axonsg-tali-0.0/c++test/libstdc++.a
/home/mike01/usr/src/axonsg-tali-0.0/c++test/libstdc++.la
/home/mike01/usr/src/axonsg-tali-0.0/c++test/libstdc++.so
/home/mike01/usr/src/axonsg-tali-0.0/c++test/libstdc++.so.3
/home/mike01/usr/src/axonsg-tali-0.0/c++test/libstdc++.so.3.0.0
# these files are the remnents of having compiled gcc 3.0
/home/mike01/gcc-3.0/libstdc++-v3
/home/mike01/gcc-3.0/libstdc++-v3/docs/html/17_intro/libstdc++-assig
n.txt
/home/mike01/gcc-3.0/libstdc++-v3/testsuite/lib/libstdc++-v3-dg.exp
/home/mike01/gcc-3.0/libstdc++-v3/testsuite/libstdc++-v3.dg
/home/mike01/gcc-obj/i586-pc-linux-gnu/libstdc++-v3
/home/mike01/gcc-obj/i586-pc-linux-gnu/libstdc++-v3/src/libstdc++.la
/home/mike01/gcc-obj/i586-pc-linux-gnu/libstdc++-v3/src/.libs/libstd
c++.so.3.0.0
/home/mike01/gcc-obj/i586-pc-linux-gnu/libstdc++-v3/src/.libs/libstd
c++.so.3
/home/mike01/gcc-obj/i586-pc-linux-gnu/libstdc++-v3/src/.libs/libstd
c++.so
/home/mike01/gcc-obj/i586-pc-linux-gnu/libstdc++-v3/src/.libs/libstd
c++.lai
/home/mike01/gcc-obj/i586-pc-linux-gnu/libstdc++-v3/src/.libs/libstd
c++.a
/home/mike01/gcc-obj/i586-pc-linux-gnu/libstdc++-v3/src/.libs/libstd
c++.la