public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Haley <aph@redhat.com>
To: Dennis Clarke <dclarke@blastwave.org>
Cc: gcc-help@gcc.gnu.org
Subject: Re: A question about RPATH
Date: Thu, 20 Dec 2012 14:51:00 -0000	[thread overview]
Message-ID: <50D325F8.6070301@redhat.com> (raw)
In-Reply-To: <fb50ee477532.50d2a9be@blastwave.org>

On 12/20/2012 11:01 AM, Dennis Clarke wrote:
> 
> 
>>> The libs fir libiconv and GNU gettext are in /usr/local/lib and not 
>>> anywhere to be found in the system lib areas : 
>>
>> The disadvantages of RPATH are well-documented.  
> 
> Really?  Name one please. 

Certainly not.  It would be way off-topic, and it's controversial and
inflammatory.  Suffice it to say that the non-usage of RPATH is
deliberate, and has been considered at length.

>> Your problem is best solved by installing dependent libraries where
>> ld.so can find them. 
> 
> Yes and no. Again I could argue the point from the perspective of
> control and quality. If I rely upon the software from the OS
> supplier ( Red Hat, Debian, Oracle ) then I must assume that the OS
> vendor is on top of things and provides reasonably up to date
> software that addresses security and feature concerns.

Well, yes.  But that has no bearing on making ld.so aware of where
you've put your libraries.

> This is rarely the case and the trade off between stability and
> feature rich end user tools is always a tough balance. I therefore
> choose to build what I want and isolate it from the OS vendor.

Your call.

>> ldconfig can do this, but if these libraries are available as
>> standard packages that's hugely preferable.
> 
> to whom ? 

Perhaps not to you.  I'm not going to argue with you.  gcc-help is not
for such things.

If you really want to build your gcc binaries with RPATH, you can do
that.

Andrew.

  reply	other threads:[~2012-12-20 14:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-19 23:08 Dennis Clarke
2012-12-19 23:21 ` Jim Rice
2012-12-19 23:57   ` Dennis Clarke
2012-12-20  0:15   ` Dennis Clarke
2012-12-20  0:19     ` Jonathan Wakely
2012-12-20  0:31       ` Dennis Clarke
2012-12-20  2:26       ` Dennis Clarke
2012-12-20  9:42 ` Andrew Haley
2012-12-20 11:01   ` Dennis Clarke
2012-12-20 14:51     ` Andrew Haley [this message]
2012-12-20 11:40   ` Jonathan Wakely
2012-12-20 14:54     ` Andrew Haley

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=50D325F8.6070301@redhat.com \
    --to=aph@redhat.com \
    --cc=dclarke@blastwave.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).