This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: why is libgcc_s.so.1 not executable?
- From: Albert Chin <gcc at mlists dot thewrittenword dot com>
- To: marek dot rouchal at infineon dot com
- Cc: gcc at gnu dot org
- Date: Fri, 7 Apr 2006 12:35:21 -0500
- Subject: Re: why is libgcc_s.so.1 not executable?
- References: <5A2C73EEAC2539458E55C514A51DCC5DF78C56@mucse304.eu.infineon.com>
- Reply-to: gcc at gnu dot org
On Fri, Apr 07, 2006 at 11:03:26AM +0200, marek.rouchal@infineon.com wrote:
> I just realized that the installation of libgcc_s.so.1 in "make install"
> is done like this
> (builfing gcc-4.0.3 on Solaris 8 / Sparc):
>
> /bin/sh ../../gcc-4.0.3/gcc/../mkinstalldirs /tmp2/gcc_4.0/lib/sparcv9;
> ginstall -c -m 644 sparcv9/libgcc_s.so.1
> /tmp2/gcc_4.0/lib/sparcv9/libgcc_s.so.1; rm -f
> /tmp2/gcc_4.0/lib/sparcv9/libgcc_s.so; ln -s libgcc_s.so.1
> /tmp2/gcc_4.0/lib/sparcv9/libgcc_s.so
>
> There is explicitely mode 644 used - in contrast to all other libs
> (libstdc++.so*, libgfortran.so*),
The other libs are libtool libs and are installed differently from
libgcc_s.so. Look at gcc/mklibgcc.in in the source directory and
gcc/libgcc.mk in the build directory.
> which are installed with 755 permissions. As a consequence, executables
> that are linked with
> libgcc_s.so.1 are not able to load it, even if the RUNPATH
> (-R/path/to/libgcc) or
> LD_LIBRARY_PATH are defined correctly.
Are you _sure_? We don't have a problem on a Solaris 8 system with
libgcc_s.so, mode 644, with either GCC 3.4.3 or 4.0.2. What error are
you getting?
--
albert chin (china@thewrittenword.com)