On 05/27/09 17:28, Matt Harrington wrote:
I'm building an RPM from this:
http://www.ysbl.york.ac.uk/~emsley/software/binaries/stable/coot-0.5.2-binary-Linux-x86_64-centos-5-gtk2.tar.gz
and rpmbuild fails because of invalid RPATHs:
<snip/>
I can circumvent this error by building like this:
QA_RPATHS=$[ 0x0001|0x0002 ] rpmbuild -ba coot.spec
However, I was wondering if there's a better way than to just ignore
this. Perhaps RPATHs could be removed entirely from the upstream
build?
Couldn't this, perhaps, be fixed using for instance chrpath (disclaimer:
I've never used it myself)? I suppose even if the rpaths were removed
by upstream, your problem wouldn't go away.
I am by no means an expert in these issues, but I firmly believe in
correct rpaths, or runpaths, or install_names, or whatever they're
called. IMHO, subsequent attempts at mending dynamic linking using
LD_LIBRARY_PATH and friends often yield situations which could make
grown men cry.
// Cheers; Johan
