In the past few weeks, I've started noticing problems with binaries
and libraries not being able to find libgcc_s.so.  I can't figure out
if it's a problem with gcc, ld or libtool.  Applications are being
linked to libgcc_s.so without the proper rpath being specified which
results in lots of problems.  I can provide the necessary -Wl,-rpath...
LDFLAGS in some Makefiles but can't figure out where to do it in some of
the more complicated build systems (glib, firefox).  My current solution
is to make a symlink to the library in /usr/lib.  Is this rpath setting
supposed to take place automatically in one of the tools or is the build
system responsible for it.  My specifications are:

% uname -srvmiop
SunOS 5.7 Generic_106541-32 sun4u sparc SUNW,Ultra-30 Solaris

% gcc -v
Reading specs from
/opt/pkg/gcc3/lib/gcc-lib/sparc-sun-solaris2/3.3.3/specs Configured
with: ./configure --prefix=/opt/pkg/gcc3 --host=sparc-sun-solaris2
--with-as=/opt/pkg/sparc-sun-solaris2/bin/as --enable-shared
--enable-languages=c : (reconfigured) ./configure
--with-gnu-ld --prefix=/opt/pkg/gcc3 --host=sparc-sun-solaris2
--with-as=/opt/pkg/sparc-sun-solaris2/bin/as --enable-shared
--enable-languages=c
Thread model: posix
gcc version 3.3.3

% ld -v
GNU ld version 2.14 20030612

% libtool --version
ltmain.sh (GNU libtool) 1.5.6 (1.1220.2.94 2004/04/10 16:27:27)
[snip copyright]
-- 
Ben Secrest <blsecres@ssdtgsm.com>