libgcc_s.so.1 yet again

[Geoff Keating]

Brad Lucier <lucier@math.purdue.edu> writes:

> Now that I'm compiling various packages with gcc-3.1 on sparcv9-sun-solaris2.8,
> I'm having libgcc_s.so.1 "issues" again.
> 
> We've been assured that there will be forward compatibility with libgcc,
> so that one can always use a newer version of libgcc with code compiled
> with an older version of gcc.  But now, I have to change my LD_LIBRARY_PATH
> every time I execute a program compiled with a different gcc-3.1 (64-bit or
> 32-bit).
> 
> So is there any way to build libgcc so that it is usable with either
> 64-bit or 32-bit applications on sparc?

Just put both directories in your LD_LIBRARY_PATH.  ld.so on Solaris
appears to be smart enough to avoid shared objects that don't match
the current ABI.

> Brad
> 
> PS:  Here is what file gives me.
> 
> banach-23% file /pkgs/gcc-3.1v9/lib/libgcc_s.so.1
> /pkgs/gcc-3.1v9/lib/libgcc_s.so.1:      ELF 64-bit MSB dynamic lib SPARCV9 Version 1, dynamically linked, not stripped
> banach-24% file /pkgs/gcc-3.1/lib/libgcc_s.so.1
> /pkgs/gcc-3.1/lib/libgcc_s.so.1:        ELF 32-bit MSB dynamic lib SPARC Version 1, dynamically linked, not stripped
> 

-- 
- Geoffrey Keating <geoffk@geoffk.org> <geoffk@redhat.com>