Bug 824810 - Boost doesn't build --without python3
Boost doesn't build --without python3
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: boost (Show other bugs)
rawhide
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Petr Machata
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-24 06:30 EDT by Radek Vokal
Modified: 2015-05-04 21:36 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-05-24 18:41:38 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Radek Vokal 2012-05-24 06:30:17 EDT
Description of problem:
Boost doesn't build --without python3


Proposed fix

diff -up boost/boost.spec.old boost/boost.spec
--- boost/boost.spec.old	2012-05-24 11:29:55.083758818 +0200
+++ boost/boost.spec	2012-05-24 11:30:11.761633553 +0200
@@ -687,7 +687,9 @@ export PATH=/bin${PATH:+:}$PATH
 %endif
 
 echo ============================= install Python 3 ==================
+%if %{with python3}
 DESTDIR=$RPM_BUILD_ROOT make -C serial-python3 VERBOSE=1 install
+%endif
 
 echo ============================= install serial ==================
 DESTDIR=$RPM_BUILD_ROOT make -C serial VERBOSE=1 install
Comment 1 Petr Machata 2012-05-24 07:28:37 EDT
D'oh.  A fixed package is building.
Comment 2 Radek Vokal 2012-05-24 07:34:04 EDT
Diky! :-)
Comment 3 Petr Machata 2012-05-24 08:10:14 EDT
We are hitting an unrelated bug on rebuild.  glibc now defines a macro named TIME_UTC, which collides with an enum value in boost::xtime_clock_typesone.
Comment 4 Petr Machata 2012-05-24 14:44:58 EDT
Upstream ticket https://svn.boost.org/trac/boost/ticket/6940
Comment 5 Petr Machata 2012-05-24 18:41:38 EDT
The build that should take care of the Python 3 problem has passed.
The TIME_UTC problem will be tracked in a separate bug 825039.

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