Open MPI logo

Hardware Locality Development Mailing List Archives

  |   Home   |   Support   |   FAQ   |   all Hardware Locality Development mailing list

Subject: Re: [hwloc-devel] [hwloc-users] hwloc and rpath
From: Jirka Hladky (jhladky_at_[hidden])
Date: 2010-06-21 16:30:36


On Monday, June 21, 2010 09:58:08 pm Jeff Squyres wrote:
> On Jun 21, 2010, at 3:18 PM, Jirka Hladky wrote:
> > $chrpath --list /usr/local/bin/lstopo
> > /usr/local/bin/lstopo: RPATH=/usr/local/lib
>
> Ah, I understand now. And I'm seeing the same behavior:
>
> $ cd util
> $ rm lstopo
> $ make V=1
> /bin/sh ../libtool --tag=CC --mode=link gcc -I/usr/include/cairo
> -I/usr/include/freetype2 -I/usr/include/libpng12 -I/usr/include/libxml2
> -std=gnu99 -fvisibility=hidden -I/home/jsquyres/hwloc-1.0.1/include
> -L/home/jsquyres/hwloc-1.0.1/src -o lstopo lstopo-lstopo.o
> lstopo-lstopo-color.o lstopo-lstopo-text.o lstopo-lstopo-draw.o
> lstopo-lstopo-fig.o lstopo-lstopo-cairo.o lstopo-lstopo-xml.o -lcairo
> -lxml2 -lz -lm -lm -lncursesw -lX11
> /home/jsquyres/hwloc-1.0.1/src/libhwloc.la libtool: link: gcc
> -I/usr/include/cairo -I/usr/include/freetype2 -I/usr/include/libpng12
> -I/usr/include/libxml2 -std=gnu99 -fvisibility=hidden
> -I/home/jsquyres/hwloc-1.0.1/include -o .libs/lstopo lstopo-lstopo.o
> lstopo-lstopo-color.o lstopo-lstopo-text.o lstopo-lstopo-draw.o
> lstopo-lstopo-fig.o lstopo-lstopo-cairo.o lstopo-lstopo-xml.o
> -L/home/jsquyres/hwloc-1.0.1/src -lcairo -lncursesw -lX11
> /home/jsquyres/hwloc-1.0.1/src/.libs/libhwloc.so -lxml2 -lz -lm -Wl,-rpath
> -Wl,/tmp/bogus/lib
>
> ...and there's the -rpath in there (my prefix was /tmp/bogus, so it's
> definitely pulling it from /home/jsquyres/hwloc-1.0.1/src/libhwloc.la).
>
> I tried building SVN with the latest latest latest GNU tools:
>
> AM 1.11.1
> AC 2.65
> LT 2.2.8
> M4 1.4.14
>
> And the same thing happened. So this is what LT wants to do. :-\
>
> We cannot be the only project that builds both LT libraries and then
> executables from those libraries. What do those projects do?

Hi Jeff,

I'm not sure what's wrong. It seems like libtool is not smart enough to
recognize /usr/lib64 as default library directory on 64-bit system.... I have
asked on Fedora packaging mailing list for advice. I will keep you updated.

>
> > Please give me a pointer to 1.0.2 version. I will give it a try, perhaps
> > it has been already fixed.
>
> My (double) bad -- the current released version is 1.0.1. We haven't
> changed anything other than Samuels' S/LIBS/LDADD/ stuff.
 No problem:-)

Thanks
Jirka