From: Paul Dubuc <pdubuc@cas.org>
To: gcc-help@gcc.gnu.org
Subject: Re: gcc can't find libgcc_s.so.1
Date: Tue, 14 Sep 2004 20:09:00 -0000 [thread overview]
Message-ID: <41474FFB.6000606@cas.org> (raw)
In-Reply-To: <4141EBB3.5010909@cas.org>
Paul Dubuc wrote:
> 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:
...
>
>
> 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?
I think I've figured it out. For any one else who might be interested, set
BOOT_LDFLAGS to the same value as LDFLAGS:
gmake \
LDFLAGS="-Wl,--rpath -Wl,${GCCRUNLIBDIR}" \
BOOT_LDFLAGS="-Wl,--rpath -Wl,${GCCRUNLIBDIR}" \
bootstrap
prev parent reply other threads:[~2004-09-14 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 18:00 Paul Dubuc
2004-09-14 20:09 ` Paul Dubuc [this message]
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=41474FFB.6000606@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).