openmpi-1.10.2 missing liboshmem [and cuda support]

Bug #1597508 reported by Erik Kruus
26
This bug affects 6 people
Affects Status Importance Assigned to Milestone
openmpi (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

A) Since ubuntu 16.04 has cuda-7.5 packages, openmpi 1.10.2 COULD be
configured --with-cuda. I need to do this, but I'm still running
ubuntu 14.04 with /usr/local/ cuda stuff so my mods are not quite correct
for ubuntu 16.04

B) liboshmem components were not being installed correctly. At least for
ubuntu 14.04, by the time debian/rules tests for the linux-only components
they have be transformed into symlinks, so the first change is
    "if test -f FOO; then \" ---> "if test -f FOO -o -h FOO; then \"
Then, there should be a few additional "mkdir -p .../man1" lines
because those directories might not yet exist under debian/PKGNAME/ yet.

Ubuntu 16.04+ SHOULD fix the liboshmem install issues
Ubuntu 16.04+ MIGHT CONSIDER doing a --with-cuda configuration.

(Unfortunately --with-cuda might be best as a new/separate package, uggh)

oh, here's the "we also need" list:
1. My release 14.04, but doing backport from 16.04 debian/
2. openmpi1.10 and related packages from openmpi-1.10.2 sources in Xenial,
   with backport mods for 14.04
3. backport should (at least) have installed liboshmem.so correctly
4. backport left dangling symlinks for liboshmem.so
   This issue should also be present in upstream 16.04 LTS,
   and is easy to fix.

Summary of my backport journey:
 openmpi (1.10.2-8ubuntu4) UNRELEASED; urgency=medium
 .
   * --with-cuda, install so.1 --> .so symlinks for new cuda libs
   * tweak library links, esp for libmca_common_cuda.so
   * fix liboshmem typo in rules file
   * rules file should test for oshrun etc. being symlinks for liboshmem stuff

Revision history for this message
Erik Kruus (ejkruus) wrote :
Revision history for this message
Erik Kruus (ejkruus) wrote :

Can someone with a working linux openmpi on 16.04 check for dangling liboshmem.so symlinks and
verify the "minor" part of this bug report?

The --with-cuda "feature request" needs careful thought/discussion,
esp. if it is to go into 16.04, since it should be coordinated with the
cuda-7.5 packages.

Revision history for this message
Joy Merwin Monteiro (joymerwin) wrote :

Hello,

I recently installed libopenmpi, and the dangling liboshmem still persists in 16.04.

Revision history for this message
Clem Wang (clemw) wrote :

I'm also having this problem.
cuda 8.0
Ubuntu 16.04

ls -al /usr/lib/liboshmem*
lrwxrwxrwx 1 root root 18 Feb 25 2016 /usr/lib/liboshmem.so -> liboshmem.so.8.1.0

But...

I did discover this:
ls -al /usr/l/lib/liboshmem*
-rwxr-xr-x 1 root root 1040 Jun 1 21:49 /usr/l/lib/liboshmem.la*
lrwxrwxrwx 1 root root 20 Jun 1 21:49 /usr/l/lib/liboshmem.so -> liboshmem.so.20.10.1*
lrwxrwxrwx 1 root root 20 Jun 1 21:49 /usr/l/lib/liboshmem.so.20 -> liboshmem.so.20.10.1*
-rwxr-xr-x 1 root root 456408 Jun 1 21:49 /usr/l/lib/liboshmem.so.20.10.1*

I'm not sure about this directory... if I accidentally created it myself or what.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in openmpi (Ubuntu):
status: New → Confirmed
Revision history for this message
J G Miller (jgmiller) wrote :

If this bug affects you, then please, please DO NOT FAIL to click the "Affects Me Too" bubble at the top of the page.

When somebody other than the original bug reporter clicks that, the status of the bug gets changed to "confirmed".

It has long been apparent policy on Launchpad that bugs which are reported but not confirmed (and are not screaming security issues) tend to be ignored and just collect dust even if a patch or solution is presented by the reporter of the bug.

The act of more people confirming the bug tends to give a bug some priority to getting a fix implemented.

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.