Hmm. This may not be pilot error. I build OMPI with a pre-installed OMPI all the time and they don't conflict during the build (i.e., the building OMPI always uses the libopen-rte and libopen-pal from the build tree, not the install tree). Here's my link lines for ompi_info:

/bin/sh ../../../libtool --tag=CXX --mode=link g++ -g -Wall -Wundef -Wno-long-long -finline-functions -pthread -export-dynamic -o ompi_info components.o ompi_info.o output.o param.o version.o ../../../ ompi/libmpi.la -lnsl -lutil -lm libtool: link: g++ -g -Wall -Wundef -Wno-long-long -finline-functions - pthread -o .libs/ompi_info components.o ompi_info.o output.o param.o version.o -Wl,--export-dynamic ../../../ompi/.libs/libmpi.so /users/ jsquyres/svn/ompi/orte/.libs/libopen-rte.so /users/jsquyres/svn/ompi/ opal/.libs/libopen-pal.so -ldl -lnsl -lutil -lm -pthread -Wl,-rpath - Wl,/home/jsquyres/bogus/lib

Notice that libopen-rte.os and libopen-pal.so are explicitly mentioned by absolute path name. Yours weren't. I wonder why...?


On May 14, 2009, at 12:41 PM, Ashley Pittman wrote:


Libtool is 2.2.6.  I use debian unstable so it's normally fairly
up-to-date, I suppose it's not impossible that a debian update has
broken things now that I think of it.

I normally build in memfs for speed and have just rebooted my machine
now, a full rebuild has failed again with the same errors.

All three symbols are shown as B according to nm so they should be
available.

Actually further testing shows it's user error again, if I remove the
current install then the build succeeds, it must have been pickings up
the libopen-pal from the install location rather than from the current
build.

Ashley Pittman,

On Thu, 2009-05-14 at 11:50 -0400, Jeff Squyres wrote:
> Hmm; odd.  I'm not getting these errors.  Just to be sure, I did a
> VPATH build and still am not getting these errors...  :-\
>
> Are those symbols publicly available in libopen-pal.so?
>
> It does seem pretty weird that your libtool link line didn't pick up
> libopen-rte.so and libopen-pal.so...? What version of LT are you using?
>
>
> On May 14, 2009, at 10:28 AM, Ashley Pittman wrote:
>
> >
> > All,
> >
> > After a svn update earlier I'm getting build failures on the trunk,
> > I've
> > tried the usual including a full clean checkout and am still getting
> > the
> > errors.
> >
> > I'm not doing anything special other than a VPATH build and this same > > tree build last week, it's just the update that appears to have broken
> > things.
> >
> > The configure line used was
> > ~/code/OpenMPI/ompi-trunk-tes/trunk/configure
> > --enable-mpirun-prefix-by-default
> > --prefix /mnt/home/debian/ashley/code/OpenMPI/install/ and I'm using
> > the
> > tree at http://svn.open-mpi.org/svn/ompi/trunk, I hope this is the
> > correct one.
> >
> > This is the error the build fails with:
> >
> > /bin/sh ../../../libtool --tag=CXX   --mode=link g++  -O3 -DNDEBUG
> > -finline-functions -pthread  -export-dynamic   -o ompi_info
> > components.o
> > ompi_info.o output.o param.o version.o ../../../ompi/libmpi.la - lnsl
> > -lutil -lm
> > libtool: link: g++ -O3 -DNDEBUG -finline-functions -pthread
> > -o .libs/ompi_info components.o ompi_info.o output.o param.o version.o > > -Wl,--export-dynamic ../../../ompi/.libs/libmpi.so -lnsl -lutil -lm > > -pthread -Wl,-rpath -Wl,/mnt/home/debian/ashley/code/OpenMPI/ install/
> > lib
> > ../../../ompi/.libs/libmpi.so: undefined reference to
> > `opal_maffinity_setup'
> > ../../../ompi/.libs/libmpi.so: undefined reference to
> > `opal_paffinity_alone'
> > ../../../ompi/.libs/libmpi.so: undefined reference to
> > `opal_paffinity_base_slot_list'
> > collect2: ld returned 1 exit status
> > make[2]: *** [ompi_info] Error 1
> > make[2]: Leaving directory `/mnt/memfs/openmpi/ompi/tools/ ompi_info'
> > make[1]: *** [all-recursive] Error 1
> > make[1]: Leaving directory `/mnt/memfs/openmpi/ompi'
> > make: *** [all-recursive] Error 1
> > ashley@alpha:/mnt/memfs/openmpi$
> >
> > I can provide more information if requested although as I say I don't
> > think I'm doing anything out of the ordinary.
> >
> > Ashley Pittman,
> >
> > _______________________________________________
> > devel mailing list
> > de...@open-mpi.org
> > http://www.open-mpi.org/mailman/listinfo.cgi/devel
>
>

_______________________________________________
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel


--
Jeff Squyres
Cisco Systems

Reply via email to