This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: objc/2940: Installation problem with libgcc_s.so
- To: mmitchel at gcc dot gnu dot org
- Subject: Re: objc/2940: Installation problem with libgcc_s.so
- From: Nicola Pero <nicola at brainstorm dot co dot uk>
- Date: Fri, 8 Jun 2001 11:07:53 +0100 (BST)
- cc: candida at tiptree dot demon dot co dot uk, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org
> Synopsis: Installation problem with libgcc_s.so
>
> State-Changed-From-To: open->closed
> State-Changed-By: mmitchel
> State-Changed-When: Thu Jun 7 15:24:57 2001
> State-Changed-Why:
> Fixed. I verified that libgcc_s.so and libgcc_s.so.0
> were installed on my GNU/Linux system, installing into a
> clean new directory.
Hi Mark,
I think the point of this bug report was not that libgcc_s.so is not
installed, but that the dynamic linker can't find it.
Unless you add the path of libgcc_s.so to your ld.so.conf and run ldconfig
- unless you do that, every Objective-C program you compile using GCC 3.0
(configured using --enable-shared) will not run because libgcc_s.so is not
found when you try running the program.
Which might not be such a problem if the fact you have to add the path to
ld.so.conf is clearly documented in capital letters somewhere prominently.