On Monday, June 21, 2010 09:07:35 pm Jeff Squyres wrote: > On Jun 21, 2010, at 12:54 PM, Jirka Hladky wrote: > > However, libtool does not look into /usr/lib64 by default. I have found 2 > > ways > > > how to fix it: > Are we installing to /usr/lib64 by default? Or do you have something in > your specfile or your system's default that is resetting libdir to > /usr/lib64?
Hi Jeff, I'm using default macro %configure in RPM spec file which will set appropriate location for libraries, binaries, etc. This is the result: ====================================================== + ./configure --build=x86_64-unknown-linux-gnu --host=x86_64-unknown-linux-gnu --target=x86_64-redhat-linux-gnu --program-prefix= --prefix=/usr --exec- prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc -- datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 -- libexecdir=/usr/libexec --localstatedir=/var --sharedstatedir=/var/lib -- mandir=/usr/share/man --infodir=/usr/share/info ====================================================== > How does one check to see if rpath was applied to the final > .libs/libhwloc.so.0.1.0? I tried objdump and didn't see anything, but I > might be looking in the wrong place: You need to check the binary, not library. I'm using chrpath utility. On my Fedora it's part of chrpath package (chrpath-0.13-6.fc12.x86_64) $which lstopo /usr/local/bin/lstopo $chrpath --list /usr/local/bin/lstopo /usr/local/bin/lstopo: RPATH=/usr/local/lib > This is definitely not a preferred solution; I don't want to get in the > business of frobbing a generated libtool script (we do it in Open MPI to > work around esoteric bugs and it's awful awful awful). I completely agree with you! Please give me a pointer to 1.0.2 version. I will give it a try, perhaps it has been already fixed. Thanks Jirka
