Ubuntu
binutils package

  1. Bug #234837
  2. Comment #10

Comment 10 for bug 234837

Revision history for this message
Cesare Tirabassi (norsetto) wrote :

motu-sru is subscribed to give clearance for uploading the fix to hardy-proposed:

1. The openmpi package is currently broken in Hardy, since it requires compilation without the -Wl,-Bsymbolic linker option. Any user attempt to initialise the library either directly or through 3rd party applications fails with a SIGSEGV.
2. The bug has been fixed in the release version by disabling dpkg-buildpackage LDFLAGS default.
3. A minimal patch applicable to the stable version of the package is attached.
4. TEST CASE:

A simple test case is defined here. It will be appreciated if users which are using the library through other applications can also confirm the fix, or otherwise.

4.1 In Hardy, install the r-cran-rmpi package with your preferred package manager. This should drag in all required dependencies, including openmpi.

4.2 Try the following simple command in a terminal:

echo 'library(Rmpi); cat("Still alive\n")' | R --slave

This should fail with a SIGSEGV (Address/Memory not mapped) signal.

4.3 Enable the hardy-proposed repository. For instance, you can do this by adding the following line to /etc/apt/sources.list:

  deb http://archive.ubuntu.com/ubuntu/ hardy-proposed universe

Update your local cache and upgrade. This should upgrade at least the following packages:

openmpi-bin, libopenmpi1, openmpi-common

4.4 Re-run the command from step 4.2 in a terminal. Initialisation should be successfull and you should see the message "Still alive" on the screen.

4.5 Disable the hardy-proposed repository.

5. There is obviously a potential for regression. I believe this is mitigated by the fact that in Debian (and Ubuntu before the dpkg-buildpackage change) this has not shown any ill effect.

WARNING: Any user willing to help with testing is more than welcome. Please be aware that there might be some time before the updated packages will be available in your mirror. The sru needs to be approved and the package manually copied by an archive admin, this may take from 1 to several days to be processed.