[Bug 136009] MakeMaker::MM_Unix doesn't honor LD_RUN_PATH requirements

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: MakeMaker::MM_Unix doesn't honor LD_RUN_PATH requirements


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=136009





------- Additional Comments From bojan at rexursive.com  2005-12-08 23:55 EST -------
If I may ask a question similar to the one in comment #19, but Perl unrelated:
what is the recommended way of building a package that ships both a library one
of its binaries depends on and the binary itself? I bumped into this problem a
while back when building (on current Rawhide) one of my (still not in FE)
packages. Basically, this is the situation:

Package is supposed to build and distribute:
- a binary (which happens to be an Apache module)
- a library to which the binary links, which will eventually be installed into
the system location (i.e. /usr/lib or /usr/lib64)

During the build (in the user's home directory), the build process encodes RPATH
of the library (something like /home/<user>/rpmbuild/blah/blah) into the binary.
One of the build scripts then checks rpaths and bombs out, saying that you can't
have that kind of stuff in the shipped binary. Which is, of course correct, but
I never asked for those to be encode in the first place ;-)

Is there a way to strip RPATHs from the libary or force some RPATHs not be
picked in some "proper" manner? I currently do this kind of trickery in my
Makefile.am to avoid the situation (basically I relink with RPATHs stripped):

eval "`eval \"echo $(LINK) $(mod_spin_la_LDFLAGS) $(mod_spin_la_OBJECTS)
$(mod_spin_la_LIBADD) $(LIBS) | sed -e s/'libtool'/'libtool -n'/ -e
s/'install-exec-hook'/'mod_spin.la'/g\" | sed -e s@'-Wl,[-]\+rpath -Wl,[^ ]\+
'@''@g -e s@'-L\(/usr\)*/lib\(64\)*\($$\| \)'@''@g`"

Ugly, error prone and most likely not generic enough. Suggestions, solutions and
advice welcome. Please be gentle, I'm no expert in this (as if that wasn't
obviuos enough already :-)

-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.