From: skelter@spamcop.net
To: gcc-help@gcc.gnu.org
Subject: RE: Why does ld insist on /lib/libgcc_so.so1
Date: Thu, 04 Dec 2003 20:44:00 -0000 [thread overview]
Message-ID: <1070570681.6tvl7f1h9vgg@webmail.spamcop.net> (raw)
Quoting lrtaylor@micron.com:
> What if you set LD_LIBRARY_PATH to the location of the correct
> libgcc_s.so.1?
Why! Then it seems to run just fine? You say the loader hits /lib and /usr/lib
first before going through the libraries described in /etc/ld.so.cache? Am I
just reading the documentation incorrectly? The man page of ld.so (8 in my
case) says the order is
DT_RPATH,LD_LIBRARY_PATH,DT_RUNPATH,/etc/ld.so.cache,trusted /lib & /usr/lib
I do not doubt that it works, or that you are correct. I am trying understand
why it does not work the way I thought it should
By the way, thank you for the help and what is your location and favorite beer?
-s
next reply other threads:[~2003-12-04 20:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-04 20:44 skelter [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-04 22:38 lrtaylor
2003-12-04 19:40 lrtaylor
2003-12-04 19:32 skelter
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=1070570681.6tvl7f1h9vgg@webmail.spamcop.net \
--to=skelter@spamcop.net \
--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).