Bug 11445 - Where is Boost_mpi?
Summary: Where is Boost_mpi?
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-11 17:45 CEST by Thomas Bigot
Modified: 2014-06-25 15:40 CEST (History)
2 users (show)

See Also:
Source RPM: boost-1.54.0-6.mga4.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Thomas Bigot 2013-10-11 17:45:46 CEST 
Description of problem:
Boost provides a component named MPI which allows to use MPI in C++ applications. This component is NOT header-only, hence there should be a libboost_mpi.so somewhere in a lib64boost_mpi package.

Version-Release number of selected component (if applicable):
1.54.0-6.mga4


urpmi lib64boost_mpi
No package named lib64boost_mpi

urpmf libboost_mpi.so
-> nothing

Reproducible: 

Steps to Reproduce:
Comment 1 Barry Jackson 2013-10-11 18:58:30 CEST 
Looking at the spec., boost is packaged to explictly exclude mpi. I have no idea why, but that seems to have been the case since pre-Mageia days before the package was originally imported.

CC: (none) => anssi.hannula, zen25000

Comment 2 Thomas Bigot 2014-02-04 11:28:56 CET 
Hi,

Are these things suppose to change ? Boost without MPI is a real problem since it prevents to run / compile any program relying on it.

Thanks in advance!
Comment 3 Barry Jackson 2014-02-05 01:45:06 CET 
(In reply to Thomas Bigot from comment #2)
> Hi,
> 
> Are these things suppose to change ? Boost without MPI is a real problem
> since it prevents to run / compile any program relying on it.
> 
> Thanks in advance!

Please test boost-1.55.0 in Cauldron which is now built with mpi support via openmpi.

Thanks.
Comment 4 Thomas Bigot 2014-06-25 15:40:15 CEST 
Sorry, I havenât been able to test it so far.
It seems to work perfectly!

Thanks!

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.