Re: lang/python27: (patch) RPATH breaking build with previous installed python27

[Matthias Ferdinand <mf+ml.pkgsrc-users%netzwerkagentursaarland.de@localhost>]

On Sun, Feb 16, 2014 at 07:54:15PM -0500, Greg Troxel wrote:
> > On Linux at least, RPATH has precedence over LD_LIBRARY_PATH. Pkgsrc
> > uses RPATH to direct its binaries to the pkgsrc installed libraries
> > instead of the system libraries.
> 
> RPATH taking precedence over LD_LIBRARY_PATH sounds broken.  Can you
> point to any specfications that say this is reasonable?

Sadly, no. Perhaps it is educational like throwing compile errors when
using open with just 2 arguments (lang/gcc3-c) :-)

> When people build python on Linux using Linux packaging systems, how
> does that work?
On Debian, neither RPATH nor RUNPATH setting is used, which avoids the
conflict.

Should be possible to add the --enable-new-dtags option only for glibc
systems. Cannot say if fixing the RPATH/LD_LIBRARY_PATH issue will
remain the only side effect of that flag. Might break someone elses
installation that relied on LD_LIBRARY_PATH being ignored by pkgsrc
packages. Might as well have more subtle failure cases while packages
using RUNPATH are mixed with ones using RPATH.

Matthias