This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Confusion with libgcc_s
- From: tim dot morse at tsc dot tdk dot com
- To: gcc-help at gcc dot gnu dot org
- Date: Thu, 12 May 2005 11:04:41 -0700
- Subject: Confusion with libgcc_s
Hi guys,
I'm having a little trouble understanding which libgcc_s.so to use when
building shared libraries
with gcc. I've looked in the newsgroups but I'm still confused.
I recently built gcc3.2.3 on a SunOS 5.8 machine and installed it in it's
own directory tree
(/usr/local/gcc-3.2.3). My understanding is that gcc is self-contained so
it knows its libgcc_s.so
is /usr/local/gcc-3.2.3/lib/libgcc_s.so.
The default gcc for the machine is v3.0.1 and was installed in /usr/local.
Its libgcc_s.so library
is in /usr/local/lib.
If I want to build a shared library, zlib for example, using gcc3.2.3, does
it matter which libgcc_s.so
I use? It seems as though I can use both -R/usr/local/lib and
-R/usr/local/gcc-3.2.3/lib and build
successfully. Is one 'better' to use than the other? The shared library
version numbers are the same
( that is, they're both libgcc_s.so.1), does that mean they are equivalent?
I've always been a little
confused about shared library versioning.
Appreciate any help, thanks.
Tim Morse