Bug 16756

Summary: boost-1.58 is missing mpi
Product: Mageia Reporter: Barry Jackson <zen25000>
Component: RPM PackagesAssignee: Shlomi Fish <shlomif>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal    
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: boost-1.58 CVE:
Status comment:
Attachments: svn diff from my working dir
iurt local build patch
boost spec

Description Barry Jackson 2015-09-15 00:31:48 CEST
Description of problem:
Boost was built with mpi in previous versions but not now.
See https://bugs.mageia.org/show_bug.cgi?id=11445

The openmpi BuildRequire is in fact still in the spec along with the "use mpi ;" which is added to the user-config.jam in a here doc.
All that is missing is the "mpi" in the %define boostlibs list.

However, it fails to create the boostlib-mpi library and there is a warning in the configuration:

warning: Graph library does not contain MPI-based parallel components.
note: to enable them, add "using mpi ;" to your user-config.jam
    - zlib                     : yes
    - iconv (libc)             : yes
    - icu                      : yes
    - compiler-supports-ssse3  : yes
    - compiler-supports-avx2   : yes
    - gcc visibility           : yes
    - long double support      : yes
warning: skipping optional Message Passing Interface (MPI) library.
note: to enable MPI support, add "using mpi ;" to user-config.jam.
note: to suppress this message, pass "--without-mpi" to bjam.
note: otherwise, you can safely ignore this message.

I have googled this and found one suggestion to add "using mpi:%{_bindir}/mpicc ;" to the user-config.jam, but this makes no difference.

I have also tried the boost-1.59 tarball with no change.

I am out of ideas, so assigning to maintainer :)

I will attach a diff of my current spec and a patch that I have made to allow it to build locally in iurt which it has never done without it.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.


Reproducible: 

Steps to Reproduce:
Comment 1 Barry Jackson 2015-09-15 00:33:25 CEST
Created attachment 7004 [details]
svn diff from my working dir
Comment 2 Barry Jackson 2015-09-15 00:35:53 CEST
Created attachment 7005 [details]
iurt local build patch

Patch that allows local build in iurt, by skipping some cat commands that try to stream here docs to the terminal, these otherwise stop the build with permission denied.
Barry Jackson 2015-09-15 00:36:52 CEST

Assignee: bugsquad => shlomif

Comment 3 Barry Jackson 2015-09-16 14:16:06 CEST
@shlomi
I have managed to hack the Fedora spec to build boost-1.59 in both mga5 and cauldron with mpi and mpich support.

Maybe you could figure out what it's doing differently to us.
Or maybe we should sync closer to Fedora (including patches) if testing shows that it breaks nothing?

I have not yet checked that the packages it produces are named like ours.

The src.rpm is here:
http://mtf.no-ip.co.uk/pub/linux/barjac/tests/boost-1.59.0-0.2.mga5.src.rpm

It's iurt build log is here:
http://mtf.no-ip.co.uk/pub/linux/barjac/distrib/cauldron/x86_64/log/boost-1.59.0-0.2.mga6.src.rpm/build.0.20150916115619.log
Comment 4 Barry Jackson 2015-09-20 16:49:51 CEST
OK I have done a lot more and now have a version that I think is fit to push. It does need a bit more work on the docs side to simplify the spec, but I think this can wait.

Of the 253 packages that use boost in Cauldron, 55 currently fail to build.

Of the remainder that do build in Cauldron, (with boost-1.58) these fail to build against boost-1.59:

aqsis
gnash
libabw
libcdr
libe-book
libreoffice
librevenge
libvisio
openfoam
paraview
quantlib
scantailor

@shlomi

I am attaching the current spec for your perusal. The srpm which still needs %mkrel bumping to 1 before pushing is here (67MB):
http://mtf.no-ip.co.uk/pub/linux/barjac/tests/boost-1.59.0-0.90.mga5.src.rpm
Comment 5 Barry Jackson 2015-09-20 16:53:05 CEST
Created attachment 7022 [details]
boost spec

Attachment 7004 is obsolete: 0 => 1

Comment 6 Barry Jackson 2016-03-13 14:02:16 CET
Fixed in 1.59 and now 1.60

Status: NEW => RESOLVED
Resolution: (none) => FIXED