> > That there looks like a build error. One should never, ever, need > to specify LD_IBRARY_PATH in order to run a binary in some location > like /opt/foo. The RPATH *should* be in the binary itself. > > > > Otherwise there is no promise that the binary will operate as > expected. > > fwiw, both debian and fedora discourage the use of RPATH > > http://wiki.debian.org/RpathIssue > http://fedoraproject.org/wiki/Packaging:Guidelines#Beware_of_Rpath
That may be, and 10,000 lemmings may run off a cliff but I will stop and say "that there, right there, is wrong". I think I'll look into the build scripts and see why the RPATH data is missing and why perfectly well built binaries don't know where to look to find the correct shared libs that are needed for them. Rather, the exec process and the dynamic run time linker should not ever need to ask a user where to find a foo.so. Otherwise I could hand craft a foo.so and stick it into my own $HOME/lib and wreck havoc perhaps? I should give that a try really. dc _______________________________________________ [email protected]: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.x.org/mailman/listinfo/xorg Your subscription address: [email protected]
