public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Dan Kegel <dank@kegel.com>
Cc: Patrick Herbst <paherbst@gmail.com>, gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: multiple installed versions of gcc -- automatically set rpath ??
Date: Fri, 29 May 2020 12:22:32 +0100	[thread overview]
Message-ID: <CAH6eHdTdNjdDuj1OQ9Eru+o8i1M-1kXfvQ8zyzE3uL_PndRWEA@mail.gmail.com> (raw)
In-Reply-To: <CAPF-yOaZNV244jxWgvDAqnA+MYpg5BuQhcqNkEb_xg6wjDcnjA@mail.gmail.com>

On Fri, 29 May 2020 at 04:53, Dan Kegel wrote:
>
> https://stackoverflow.com/questions/13334300/how-to-build-and-install-gcc-with-built-in-rpath
> is a bit dated, but might be helpful.  It says in part:
> 
> Using --with-boot-ldflags="-Wl,-rpath,/some/path" on the configure
> step seems to work for me on gcc 4.8.3. The docs discuss this a bit
> https://gcc.gnu.org/install/configure.html

That sets the linker flags to use when building GCC itself. It doesn't
make GCC automatically add those linker flags when you compile your
own programs.

Even if it did add the flags when compiling your own programs, it
wouldn't work well for multlib compilers where the rpath should be lib
or lib64 depending on the multilib being used for a given compilation.

  parent reply	other threads:[~2020-05-29 11:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-29  2:54 Patrick Herbst
2020-05-29  3:07 ` Dan Kegel
2020-05-29  9:28   ` Patrick Bégou
2020-05-29 11:02     ` Thomas Doczkal
2020-05-29 11:22   ` Jonathan Wakely [this message]
2020-05-29 11:33 ` Jonathan Wakely
2020-05-29 17:23   ` Jonathan Wakely

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=CAH6eHdTdNjdDuj1OQ9Eru+o8i1M-1kXfvQ8zyzE3uL_PndRWEA@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=dank@kegel.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=paherbst@gmail.com \
    /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).