Strange rpath behavior

[Jorge Gallegos]

Hi,

I am looking for a sponsor for uwsgi server in this ticket
https://bugzilla.redhat.com/show_bug.cgi?id=682704 however I am trying
to fix the rpath issues I commented there because otherwise i think it
simply won't pass. I am faced with some... weird behavior.

The software does not use the standard configure/makefile approach,
instead it is built using a python program (uwsiconfig.py) to decide
what flags it should use, then simply calls them (os.system(bla)) to
build it.

When I build the package using the python program I get warnings about
rpath being present (sure enough I inspect the binaries and I can
see /usr/lib64 in there) but, when I basically pipe the output of the
program to another shell file (sans comments) and execute that shell
file, I get no warning whatsoever and /usr/lib64 is nowhere to be found
in the binaries.

Now, I could cheat and patch uwsgiconfig.py to write the shell script
instead of calling os.system (actually I have a patch/spec I just tested
and works just fine) but that sounds like bad form. Can any of you
veterans tell me why this is happening?

My initial thought would be: "python _has_ rpath issues, which the
binaries inherit because they are compiled under python's scope"

Thoughts?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
Url : http://lists.fedoraproject.org/pipermail/devel/attachments/20110813/f42acc48/attachment.bin