Hi, I attach both $builddir/ompi/libmpi.la and /usr/lib/libosmcomp.la (both from a system where I kept that file).
/usr/lib/libosmcomp.la has no embedded rpath information. FWIW, this .la file comes from the file MLNX_OFED_LINUX-3.1-1.0.3-debian8.1-x86_64/DEBS/libopensm_4.6.0.MLNX20150830.c69ebab_amd64.deb . On Sat, Feb 27, 2016 at 2:22 PM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> wrote: > Does /usr/lib/libosmcomp.la contain the -L/usr/lib flag, or rpath it? neither, as far as I can tell; but maybe you want to inspect the attached file if it looks bogus. I see no explicit tinkering with linker flags in the .la file. It looks as if libtool, because it gets fed /usr/lib/libosmcomp.la, decides that it needs to append -L/usr/lib and -losmcomp to the gcc command line. Which would be fine if we had not -lopen-rte later... What's the dependency chain which makes libmpi.la pull libosmcomp among its dependent libs ? Best, E. > > If so, then Open MPI has no way of knowing that a given dependent library's > .la file is faulty (i.e., inserting -L / etc. flags that point to > linker-default locations). The real fix would be to fix > /usr/lib/libosmcomp.la. > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > _______________________________________________ > users mailing list > us...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users > Link to this post: > http://www.open-mpi.org/community/lists/users/2016/02/28598.php
libmpi.la
Description: application/shared-library-la
libosmcomp.la
Description: application/shared-library-la
