Bug 1105088 - thin-provisioning-tools - Fails to build with Boost 1.68.0
thin-provisioning-tools - Fails to build with Boost 1.68.0
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Basesystem
Other Other
: P5 - None : Normal (vote)
: ---
Assigned To: Martin Pluskal
E-mail List
Depends on:
Blocks: 1105081
  Show dependency treegraph
Reported: 2018-08-16 14:13 UTC by Adam Majer
Modified: 2018-08-20 08:32 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Adam Majer 2018-08-16 14:13:23 UTC
New Boost library has been released and unfortunately this package fails to build with it. The new boost library is soon submitted to devel:libraries:c_c++/boost and will be submitted to openSUSE:Factory shortly.


> [  104s] g++ -c -I. -I. -I./thin-provisioning -fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fs
> tack-protector-strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection -g -Wall -fPIC -fno-strict-a
> liasing -std=c++11 -DDEV_TOOLS -fmessage-length=0 -grecord-gcc-switches -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-
> strong -funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection  -DSTRERROR_R_CHAR_P  -o thin-provisioning/
> thin_show_metadata.o thin-provisioning/thin_show_metadata.cc
> [  104s] thin-provisioning/thin_show_duplicates.cc:43:10: fatal error: boost/uuid/sha1.hpp: No such file or directory
> [  104s]  #include <boost/uuid/sha1.hpp>
> [  104s]           ^~~~~~~~~~~~~~~~~~~~~
> [  104s] compilation terminated.
> [  104s] make: *** [Makefile:205: thin-provisioning/thin_show_duplicates.o] Error 1
> [  104s] make: *** Waiting for unfinished jobs....

Sha1 support was removed from Uuid library,

Comment 1 Adam Majer 2018-08-20 07:38:43 UTC
fix submitted to factory
Comment 2 Martin Pluskal 2018-08-20 08:32:33 UTC
(In reply to Adam Majer from comment #1)
> fix submitted to factory

Thanks a lot for fixing the issue!