libtool-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] new -no-rpath option to disable hardcoding of library paths


From: Scott James Remnant
Subject: Re: [PATCH] new -no-rpath option to disable hardcoding of library paths
Date: Tue, 04 Nov 2003 00:06:05 +0000

On Tue, 2003-11-04 at 00:01, Peter O'Gorman wrote:

> Scott James Remnant wrote:
> 
> > Are there any platforms that don't allow not hardcoding the path even
> > when used with shlibpath_ver?  Comments in libtool seem to indicate this
> > would work.
> 
> I also don't see how you got from adding /usr/X11R6/lib to 
> sys_lib_dlsearch_path_spec to a whole new option to libtool. I don't 
> like this much, nor do I see the need for it.
> 
> If you really want something like this applied, you'll have to explain 
> why. The reasons you gave for having /usr/X11R6/lib in 
> sys_lib_dlsearch_path_spec for linux seemed a little iffy anyway, but 
> since it only changed a single platform and was easy to revert I was 
> willing to give it a try. This one will require a much better argument :)
> 
Well, the actual reason is that it is considered bad practice for Debian
packages to contain libraries with RPATHs in them.  (I did mention it
was an itch).

So in order to comply with that, our package maintainers need a version
of libtool that doesn't RPATH libraries (specifically in /lib, /usr/lib
and /usr/X11R6/lib).

If the Debian libtool package has this, it ends up in all sorts of
pieces of software anyway, so makes some vague sense to have the same
option upstream otherwise things will get horribly out of sync again.

Scott
-- 
"Fucking moron. You are an ass hole."

   -- Christian Marillat <address@hidden> doesn't like bugs in
      general, let alone people fixing them for him.

Attachment: signature.asc
Description: This is a digitally signed message part


reply via email to

[Prev in Thread] Current Thread [Next in Thread]