Open MPI logo

Hardware Locality Users' Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [hwloc-users] hwloc and rpath
From: Samuel Thibault (samuel.thibault_at_[hidden])
Date: 2010-06-18 19:10:21

Jirka Hladky, le Sat 19 Jun 2010 00:45:17 +0200, a écrit :
> I haven't tried it yet. In any case, rpath is already in which is
> shipped with hwloc-1.0.1:
> ./src/ = -rpath
> $(libdir)
> ./src/ =
> ./src/ $(AM_V_CCLD)$(libhwloc_la_LINK) $(am_libhwloc_la_rpath)
> $(libhwloc_la_OBJECTS) $(libhwloc_la_LIBADD) $(LIBS)
> ./src/ $(AM_V_CCLD)$(libhwloc_embedded_la_LINK)

Yes, because at that stage it can't know whether libdir will be in the
standard search path or not. But then libtool filters this out, see

/bin/sh ../libtool --tag=CC --mode=link gcc -std=gnu99 -fvisibility=hidden -I/usr/include/libxml2 -std=gnu99 -fvisibility=hidden -Wall -g -I/home/samy/pm2-newsched/hwloc/include -Wall -Wunused-parameter -Wundef -Wno-long-long -Wsign-compare -Wmissing-prototypes -Wstrict-prototypes -Wcomment -pedantic -no-undefined -version-number 0:0:0 -lxml2 -o -rpath /usr/local/lib topology.lo traversal.lo topology-synthetic.lo bind.lo cpuset.lo misc.lo topology-xml.lo topology-linux.lo topology-x86.lo -libverbs
libtool: link: gcc -shared .libs/topology.o .libs/traversal.o .libs/topology-synthetic.o .libs/bind.o .libs/cpuset.o .libs/misc.o .libs/topology-xml.o .libs/topology-linux.o .libs/topology-x86.o /usr/lib/ /usr/lib/ -Wl,-soname -Wl, -o .libs/

> > So apparently libtool somehow doesn't realizes that /usr/lib64 is in the
> > standard search path. I'd tend to believe it's a bug in libtool or the
> > distribution which don't understand each other. How does configure get
> > invoked? What is the output of gcc -print-search-dirs?
> I have double checked it.
> /usr/lib64 is included in the output of gcc -print-search-dirs.