Bug 1258128 - librevenge FTBFS in rawhide with Boost 1.59.0
librevenge FTBFS in rawhide with Boost 1.59.0
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: librevenge (Show other bugs)
rawhide
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: David Tardon
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-29 08:10 EDT by Jonathan Wakely
Modified: 2015-08-30 08:25 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-08-30 02:40:44 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)
build.log from failed scratch build with boost-1.59.0 (114.86 KB, text/plain)
2015-08-29 08:10 EDT, Jonathan Wakely
no flags Details
Patch for the rawhide spec file. (3.12 KB, patch)
2015-08-29 08:21 EDT, Jonathan Wakely
no flags Details | Diff

  None (edit)
Description Jonathan Wakely 2015-08-29 08:10:40 EDT
Created attachment 1068273 [details]
build.log from failed scratch build with boost-1.59.0

I'm updating Boost in rawhide and librevenge fails to build with a linker error:

../lib/.libs/librevenge-0.0.so: undefined reference to `boost::system::system_category()'
../lib/.libs/librevenge-0.0.so: undefined reference to `boost::system::generic_category()'
collect2: error: ld returned 1 exit status
Makefile:623: recipe for target 'testfileinfo' failed

This can be reproduced with:

fedpkg scratch-build --target f24-boost

(The f24-boost tag contains the updated boost-1.59.0 builds).

Scratch build:
https://koji.fedoraproject.org/koji/taskinfo?taskID=10861500
Comment 1 Jonathan Wakely 2015-08-29 08:21:30 EDT
Created attachment 1068274 [details]
Patch for the rawhide spec file.

This patch fixes it, but is a kluge. Please let me know ASAP if you would prefer to fix it differently or if I can go ahead and make this change for now.
Comment 2 David Tardon 2015-08-30 02:40:44 EDT
Already fixed upstream.
Comment 3 Jonathan Wakely 2015-08-30 08:25:58 EDT
Aha, thanks

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