Re: [COOT] use of RPATH in coot libraries

2009-06-02 Thread Winter, G (Graeme)
: Re: use of RPATH in coot libraries Peter Keller wrote: On Mon, 1 Jun 2009, Kevin Cowtan wrote: OK, I understand, RPATH bad. But as far as I can tell we don't use RPATH. Coot uses LD_LIBRARY_PATH, which is only set by a wrapper script which launches the actual binary, and so the use

Re: [COOT] use of RPATH in coot libraries

2009-06-02 Thread Clemens Vonrhein
Hi Kevin, On Tue, Jun 02, 2009 at 09:16:54AM +0100, Kevin Cowtan wrote: On the whole, I prefer to use rpath, because it makes it easier to harden an installation against the vagaries of what users have set in their environment - using an rpath like '$ORIGIN/../lib' to set a path

Re: [COOT] use of RPATH in coot libraries

2009-06-02 Thread Clemens Vonrhein
Hi Kevin, On Tue, Jun 02, 2009 at 02:18:25PM +0100, Kevin Cowtan wrote: OK, that is pretty cool, looks like the correct technical solution for our relocatable binaries. Yes - Peter did some great analysis of all this on Linux and OsX. I can see implementation problems. It looks to me as

Re: [COOT] use of RPATH in coot libraries

2009-06-02 Thread Ballard, CC (Charles)
: [COOT] use of RPATH in coot libraries Hi Kevin, On Tue, Jun 02, 2009 at 02:18:25PM +0100, Kevin Cowtan wrote: OK, that is pretty cool, looks like the correct technical solution for our relocatable binaries. Yes - Peter did some great analysis of all this on Linux and OsX. I can see

Re: [COOT] use of RPATH in coot libraries

2009-06-01 Thread Kevin Cowtan
Τι γλώσσα είναι ομιλίας σας? Ezra Peisach wrote: One of the other misfeatures of rpath is that it sets DT_RPATH and not DT_RUNPATH - which means that LD_LIBRARY_PATH will not override the setting... This means if you have a library installed in the RPATH and you set LD_LIBRARY_PATH (for in

Re: [COOT] use of RPATH in coot libraries

2009-06-01 Thread Matt Harrington
On Mon, Jun 1, 2009 at 1:14 AM, Kevin Cowtan cow...@ysbl.york.ac.uk wrote: Τι γλώσσα είναι ομιλίας σας? This should shed some light on the subject: http://en.wikipedia.org/wiki/Rpath_(linking) Matt

Re: [COOT] use of RPATH in coot libraries

2009-06-01 Thread Kevin Cowtan
OK, I understand, RPATH bad. But as far as I can tell we don't use RPATH. Coot uses LD_LIBRARY_PATH, which is only set by a wrapper script which launches the actual binary, and so the use of LD_LIBRARY_PATH is never exposed to the rest of the system (which I understand is the only problem

Re: [COOT] use of RPATH in coot libraries

2009-06-01 Thread Kevin Cowtan
Oh, hang on. If I do: objdump -p `which coot-real` | grep RPATH then I get: RPATH /y/people/emsley/autobuild/Linux-bragg1.chem.york.ac.uk-pre-release-gtk2/lib I can't see where that is coming from, but I'm pretty sure it is redundant, since that directory doesn't exist on the machine

Re: [COOT] use of RPATH in coot libraries

2009-06-01 Thread Ezra Peisach
If you link against a library that has rpath defined - you will inherit it in the executable... So - the following have rpath hardwired in from the autobuild script libgreg libgtkglext-x11 libguile* libreadline libhistory And I do not know which library depends on the others So - it

Re: [COOT] use of RPATH in coot libraries

2009-06-01 Thread Johan Hattne
On 06/01/09 10:12, Ezra Peisach wrote: If you link against a library that has rpath defined - you will inherit it in the executable... But this is intended behaviour? If I compile against ${HOME}/lib/libguile* I wouldn't want the runtime linker to use /usr/lib/libguile*, because presumably my

Re: [COOT] use of RPATH in coot libraries

2009-06-01 Thread Ezra Peisach
Johan Hattne wrote: On 06/01/09 10:12, Ezra Peisach wrote: If you link against a library that has rpath defined - you will inherit it in the executable... But this is intended behaviour? If I compile against ${HOME}/lib/libguile* I wouldn't want the runtime linker to use

Re: [COOT] use of RPATH in coot libraries

2009-06-01 Thread Johan Hattne
On 06/01/09 12:49, Kevin Cowtan wrote: Johan Hattne wrote: But this is intended behaviour? If I compile against ${HOME}/lib/libguile* I wouldn't want the runtime linker to use /usr/lib/libguile*, because presumably my build requires something that /usr/lib/libguile doesn't provide. Don't

Re: [COOT] use of RPATH in coot libraries

2009-05-31 Thread Matt Harrington
On Thu, May 28, 2009 at 9:45 PM, Johan Hattne johan.hat...@utsouthwestern.edu wrote: 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

Re: [COOT] use of RPATH in coot libraries

2009-05-31 Thread Matt Harrington
On Fri, May 29, 2009 at 9:38 AM, Tim Fenn f...@stanford.edu wrote: I'm not sure if this will help: http://www.stanford.edu/~fenn/packs/coot-0.5.2-3.fc11.src.rpm but you'll need the dependencies as well (which distribution are you using?) Many thanks for that, Tim. It's always helpful

Re: [COOT] use of RPATH in coot libraries

2009-05-31 Thread Ezra Peisach
One of the other misfeatures of rpath is that it sets DT_RPATH and not DT_RUNPATH - which means that LD_LIBRARY_PATH will not override the setting... This means if you have a library installed in the RPATH and you set LD_LIBRARY_PATH (for in tree development - or old installation and a new

Re: [COOT] use of RPATH in coot libraries

2009-05-29 Thread Tim Fenn
On Thu, 28 May 2009 23:45:24 -0500 Johan Hattne johan.hat...@utsouthwestern.edu wrote: 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