public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Andy Freeman" <anamax@earthlink.net> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: bootstrap/7323: Install failed to property account for libstdc++ location Date: Mon, 15 Jul 2002 22:56:00 -0000 [thread overview] Message-ID: <20020716055601.24511.qmail@sources.redhat.com> (raw) The following reply was made to PR bootstrap/7323; it has been noted by GNATS. From: "Andy Freeman" <anamax@earthlink.net> To: "Andrew Pinski" <pinskia@physics.uc.edu> Cc: <gcc-gnats@gcc.gnu.org> Subject: Re: bootstrap/7323: Install failed to property account for libstdc++ location Date: Mon, 15 Jul 2002 22:52:12 -0700 Huh? I suspect g++/ld knew where the correct library was when they generated the executable, so why isn't that info in the executable for startup? Why is it a good thing that it isn't? In other words, are you saying that I have to set LD_LIBRARY_PATH correctly before I start each executable.... (There are at least two ways to end up with different libraries that have the same base name+extension, so if the lookup is by file base name+extension, there's no way to have a single LD_LIBRARY_PATH that is always correct at startup.) -andy ----- Original Message ----- From: "Andrew Pinski" <pinskia@physics.uc.edu> To: <anamax@earthlink.net> Cc: <gcc-gnats@gcc.gnu.org> Sent: Monday, July 15, 2002 9:40 PM Subject: Re: bootstrap/7323: Install failed to property account for libstdc++ location > The fix is really to set LD_LIBRARY_PATH to include your prefix: > /home/andy/GCC3.1/gcc-3.1-bin. > > This is because gcc now uses shared libraries and you did not > install gcc where ld*.so find them. > > Thanks, > Andrew Pinski >
next reply other threads:[~2002-07-16 5:56 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-07-15 22:56 Andy Freeman [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-05-14 10:53 giovannibajo 2003-05-14 9:26 Dara Hazeghi 2002-07-15 21:46 Andrew Pinski 2002-07-15 21:36 anamax
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=20020716055601.24511.qmail@sources.redhat.com \ --to=anamax@earthlink.net \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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: linkBe 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).