openmpi-dev depends on libibverbs-dev

Bug #342344 reported by Olaf Lenz
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
openmpi (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I'm using openmpi on Jaunty.

It looks as though libopenmpi-dev does not depend on libibverbs-dev, but it should.
When I try to link a program and libopenmpi-dev is installed, but libibverbs-dev is not, I get an error:

bin/bash ../../libtool --tag=CXX --mode=link mpic++ -Wall -L/home/olenz/software/lib -o libesutil.la bindings.lo TupleVector.lo Timer.lo
/bin/grep: /usr/lib/libibverbs.la: No such file or directory
/bin/sed: can't read /usr/lib/libibverbs.la: No such file or directory
libtool: link: `/usr/lib/libibverbs.la' is not a valid libtool archive

When I install libibverbs-dev, the error is gone. This looks to me as though the dependencies of libopenmpi-dev should include libibverbs-dev.

However, as far as I understand, libibverbs is an infiniband library. In principle, I do not see a reason why I do have to install a library for a hardware that I do not have on my laptop.

Revision history for this message
Nizamov Shawkat (nizamov-shawkat) wrote :

I also hit this bug. I am compiling the package, depending on openmpi (in my ppa).
It was a big surprise to see build failed because package was perfectly buildable package in pbuilder on my desktop.
Interestingly, build fails only on lpia architecture and succeeds on i386 and x86_64 arch's.

/bin/bash ../libtool --tag=CXX --mode=link mpic++ -g -O2 -version-info 3:0:0 -Wl,-Bsymbolic-functions -o libmeep_mpi.la -rpath /usr/lib anisotropic_averaging.lo bands.lo boundaries.lo bicgstab.lo control_c.lo cw_fields.lo dft.lo energy_and_flux.lo fields.lo loop_in_chunks.lo grace.lo h5fields.lo h5file.lo initialize.lo integrate.lo monitor.lo mympi.lo output_directory.lo polarization.lo sources.lo step.lo step_db.lo structure.lo time.lo update_eh.lo mpb.lo update_pols.lo vec.lo step_generic.lo -lhdf5 -lz -lgsl -L/usr/lib/gcc/i686-linux-gnulp/4.2.3 -L/usr/lib/gcc/i686-linux-gnulp/4.2.3/../../.. -lharminv -llapack -lblas -lgfortranbegin -lgfortran -lm -lgcc_s -lfftw3 -lm
/bin/grep: /usr/lib/libibverbs.la: No such file or directory
/bin/sed: can't read /usr/lib/libibverbs.la: No such file or directory
libtool: link: `/usr/lib/libibverbs.la' is not a valid libtool archive
make[4]: *** [libmeep_mpi.la] Error 1
make[4]: Leaving directory `/build/buildd/meep-0.20.4/debian/build-openmpi/src'
make[3]: *** [all] Error 2
make[3]: Leaving directory `/build/buildd/meep-0.20.4/debian/build-openmpi/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/build/buildd/meep-0.20.4/debian/build-openmpi'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/build/buildd/meep-0.20.4/debian/build-openmpi'
make: *** [build-stamp-openmpi] Error 2
dpkg-buildpackage: failure: debian/rules build gave error exit status 2

Revision history for this message
Nizamov Shawkat (nizamov-shawkat) wrote :

> Interestingly, build fails only on lpia architecture and succeeds on i386 and x86_64 arch's.

even more - build fails only on lpia on jaunty and hardy, but not on the intrepid

Revision history for this message
James Page (james-page) wrote :

I believe this issue has been resolved in the current version of openmpi in Ubuntu - marking 'Fix Released'

Changed in openmpi (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.