Bug 1451982 - Missing Boost.Python NumPy extension
Summary: Missing Boost.Python NumPy extension
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: boost
Version: 26
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jonathan Wakely
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-18 05:50 UTC by Yaakov Selkowitz
Modified: 2017-09-26 23:56 UTC (History)
6 users (show)

Fixed In Version: boost-1.63.0-8.fc26
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-09-26 23:56:31 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Patch for rawhide (23.58 KB, patch)
2017-05-25 03:04 UTC, Yaakov Selkowitz
no flags Details | Diff
Patch v2 (24.50 KB, patch)
2017-05-29 04:47 UTC, Yaakov Selkowitz
no flags Details | Diff

Description Yaakov Selkowitz 2017-05-18 05:50:13 UTC
Since boost 1.63.0, new libboost_numpy{,3} libraries would be built if python{2,3}-numpy is added to {Build,}Requires.  Unfortunately, there appears to be a(nother) bug in Boost.Jam which prevents building for both Python 2 and 3 simultaneously when numpy is enabled, so this will take some more hacking.

Once that is fixed, then the question is whether libboost_numpy{,3} should be packaged together with libboost_python{,3} or separately.

Comment 1 Jonathan Wakely 2017-05-18 09:17:33 UTC
I refuse to touch Boost.Jam, it's voodoo. It will need to be addressed upstream, or we'll need to stop trying to build Python 2 and 3 at the same time (as per Bug 1420086 comment 13).

Comment 2 Yaakov Selkowitz 2017-05-19 18:11:14 UTC
I'm working on a patch based on not trying to build them simultaneously, but not building everything twice either.  Would you prefer libboost_numpy* to be packaged together with the respective libboost_python* or separately (they will need a Requires: python*-numpy)?

Comment 3 Jonathan Wakely 2017-05-22 09:42:42 UTC
Great, thanks for battling the build system. I think we should have new boost-numpy{,3} packages, separate from the boost-python{,3} ones.

Comment 4 Yaakov Selkowitz 2017-05-25 03:04:14 UTC
Created attachment 1282108 [details]
Patch for rawhide

- Add numpy and numpy3 packages
- Add openmpi-python3 and mpich-python3 packages
- Add missing ldconfig post/postun for python3 package

Scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=19720894

Comment 5 Yaakov Selkowitz 2017-05-29 04:47:01 UTC
Created attachment 1283161 [details]
Patch v2

- Add numpy and numpy3 packages (#1451982)
- Fix location of openmpi-python and mpich-python modules
- Add openmpi-python3 and mpich-python3 packages
- Add missing ldconfig post/postun for python3 package

Scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=19757249

Comment 6 Jonathan Wakely 2017-07-01 19:41:21 UTC
Thanks, patch committed and built  for rawhide:
https://koji.fedoraproject.org/koji/buildinfo?buildID=914400

It looks like the changes to libs/python/build/Jamfile are not needed for Boost 1.64.0 so I'll drop that part of the patch when I rebase boost in rawhide (probably some time next week).

Comment 7 Stefan Seefeld 2017-08-04 13:25:40 UTC
Please backport to F26. Thanks !

Comment 8 Fedora Update System 2017-09-24 00:28:11 UTC
boost-1.63.0-8.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-b189dbbd55

Comment 9 Fedora Update System 2017-09-25 06:20:49 UTC
boost-1.63.0-8.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-b189dbbd55

Comment 10 Fedora Update System 2017-09-26 23:56:31 UTC
boost-1.63.0-8.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.