On Tue, Jun 27, 2006 at 03:48:30AM -0400, Paul Hilfinger wrote:
>
> I guess that I'm simply suggesting that it might be nice if the sort
> of modification suggested by Albert Chin's response to my question
> could be installed automatically under control of a configuration
> option (e.g.), or as a
> > 2. Remember to include the appropriate -W,l-R option or whatever in
> >[each] and every compilation.
>
> I don't think it's a good idea to compile in rpaths to non-standard
> (user-specific) directories by default. This can lead to trapdoor
> rpaths and generally makes the binaries less
> I don't think it's a good idea to compile in rpaths to non-standard
> (user-specific) directories by default.
Whether it should be the default is debatable and different people will
have different opinions.
Whether there should be an option to do that seems very useful and
desirable to me. That
* Paul Hilfinger:
> 2. Remember to include the appropriate -W,l-R option or whatever in
>and every compilation.
I don't think it's a good idea to compile in rpaths to non-standard
(user-specific) directories by default. This can lead to trapdoor
rpaths and generally makes the binaries less p
On Sun, Jun 25, 2006 at 07:47:52PM -0400, Paul Hilfinger wrote:
>
> I have a situation (on Linux or Solaris, at least), in which I
> install versions of GCC in non-standard directories (specifically,
> directories not owned & operated by root). With such an
> installation, when a GCC link finds a
