From: Paul Dubuc <pdubuc@cas.org>
To: gcc-help@gcc.gnu.org
Subject: gcc can't find libgcc_s.so.1
Date: Fri, 10 Sep 2004 18:00:00 -0000 [thread overview]
Message-ID: <4141EBB3.5010909@cas.org> (raw)
I'm having trouble building gcc (3.3.4 on Solaris 8 Sparc) so that it doesn't
need the location of libgcc_s.so.1 in LD_LIBRARY_PATH. I thought I could do
this in the bootstrap step by saying
gmake LDFLAGS="-Wl,--rpath -Wl,${GCCRUNLIBDIR}" bootstrap
or
gmake LDFLAGS="-R${GCCRUNLIBDIR}" bootstrap
this has worked in the past when libstdc++.so developed a dependency on this
library:
dump -Lv libstdc++.so
libstdc++.so:
**** DYNAMIC SECTION INFORMATION ****
.dynamic:
[INDEX] Tag Value
[1] NEEDED libm.so.1
[2] NEEDED libgcc_s.so.1
[3] NEEDED libc.so.1
[4] SONAME libstdc++.so.5
[5] RPATH /volws/pmd25/ldatae/gnu/gcc-3.3.4/lib
[6] INIT 0x26468
[7] FINI 0x5c970
[8] HASH 0x94
...
The RPATH is the location of libgcc_s.so.1. Now, I notice that the gcc and g++
executables also have this dependency:
dump -Lv g++
g++:
**** DYNAMIC SECTION INFORMATION ****
.dynamic:
[INDEX] Tag Value
[1] NEEDED libgcc_s.so.1
[2] NEEDED libc.so.1
[3] INIT 0x11468
[4] FINI 0x25778
[5] HASH 0x100e8
This wasn't the case in 3.3.1
How do I run gmake bootstrap to get the RPATH into the executable so I don't get
ld.so.1: ./g++: fatal: libgcc_s.so.1: open failed: No such file or directory
Killed
when I run the compiler and so I don't have to set LD_LIBRARY_PATH?
Any help would be appreciated.
--
Paul M. Dubuc
next reply other threads:[~2004-09-10 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 18:00 Paul Dubuc [this message]
2004-09-14 20:09 ` Paul Dubuc
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4141EBB3.5010909@cas.org \
--to=pdubuc@cas.org \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).