public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: kevin diggs <diggskevin38@gmail.com>
Cc: Kai Ruottu <kai.ruottu@wippies.com>, gcc-help@gcc.gnu.org
Subject: Re: gcc 4.6.0
Date: Thu, 09 Jun 2011 04:26:00 -0000	[thread overview]
Message-ID: <BANLkTikJ2sF6GW+AsCWufPfWmGZxieOv7Q@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi==x79ODCExVQD+mbP3PDZSNNurow@mail.gmail.com>

On 8 June 2011 18:52, kevin diggs wrote:
> Hi,
>
> On Tue, Jun 7, 2011 at 5:53 PM, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
>>
>> If by "self rpath" you mean setting rpath to the directory where gcc
>> is installed that won't help when people have installed gmp, mpfr and
>> mpc elsewhere (which they often do)
>>
> No, I mean adding an rpath with the path for these trouble makers into
> "whatever" in gcc needs to find them. A specific rpath isn't tied to a
> particular library, is it? For example if I build gcc using particular
> revision of gmp in a particular spot (hacked to include an rpath to
> find it). And then download and build a minor rev to gmp in a
> different place and remove the original. If I tell the dynamic linker
> about the new gmp will gcc still run?

Yes

>> See http://gcc.gnu.org/faq.html#rpath for why GCC doesn't set rpath
>> automatically, unlike some other compilers.
>>
> Thanks for the link. I'll take a look.
>
>> If you want it to have an rpath you have that option, using
>> appropriate linker flags or the LD_RUN_PATH environment variable.
>>
> Is this env in the install manual? I'll take a peek. Might give it a try.

Try "man ld"

  reply	other threads:[~2011-06-08 22:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-04 17:44 Bill Cunningham
2011-06-04 17:49 ` Axel Freyn
2011-06-04 17:56 ` Jonathan Wakely
2011-06-04 18:28   ` Bill Cunningham
2011-06-04 18:51     ` Jonathan Wakely
2011-06-06 21:13       ` kevin diggs
2011-06-07  0:03         ` Kai Ruottu
2011-06-07  7:54           ` Jonathan Wakely
2011-06-07  8:09             ` Jonathan Wakely
2011-06-07 19:40               ` kevin diggs
2011-06-08  6:05                 ` Jonathan Wakely
2011-06-08  9:05                   ` Jonathan Wakely
2011-06-08 11:09                   ` Andrew Haley
2011-06-08 12:03                     ` Jonathan Wakely
2011-06-08 22:14                   ` kevin diggs
2011-06-09  4:26                     ` Jonathan Wakely [this message]
2011-06-07 19:55   ` David Kirkby

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=BANLkTikJ2sF6GW+AsCWufPfWmGZxieOv7Q@mail.gmail.com \
    --to=jwakely.gcc@gmail.com \
    --cc=diggskevin38@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=kai.ruottu@wippies.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).