Bugzilla – Bug 1089801
[TRACKER BUG] Boost upgrade to 1.67.0 compilation issues
Last modified: 2018-08-16 13:40:41 UTC
Boost 1.67.0 has implemented some breaking changes in certain libraries that result in a number of build failures. These are tracked here before new Boost enters factory.
Current version of Boost 1.67.0 resides in home:adamm:boost_test on OBS. Blocking bugs are tracking fixes to allow simpler transition once new Boost is submit to Factory. Please fix packages (or other packages), test build against home:adamm:boost_test/boost, close blocking bugs and and submit to Factory.
Maybe a bit late, because boost67 had just been included in TW. Still: Compiling PlanetaryImager I get a build error /usr/include/boost/lockfree/spsc_queue.hpp:145:51: error: ‘next’ is not a member of ‘boost’ searchin the web I found https://svn.boost.org/trac10/ticket/13497 which points to a patch in the git repo that probably needs to be included in the TW build?
(In reply to Peter Sütterlin from comment #2) > Maybe a bit late, because boost67 had just been included in TW. Still: > Compiling PlanetaryImager I get a build error > /usr/include/boost/lockfree/spsc_queue.hpp:145:51: error: ‘next’ is not a > member of ‘boost’ > > searchin the web I found https://svn.boost.org/trac10/ticket/13497 which > points to a patch in the git repo that probably needs to be included in the > TW build? That problem can be fixed in Boost, but also can be (temporarily) fixed in the PlanetaryImager sources. Please add, #include <boost/next_prior.hpp> before including the lockfree module and it should compile OK. Next Boost version will be out in August and that header fix should be then included.
Yes, I added that line myself (in spsc_queue.hpp of boost, else I'd have to 'fix' all packages using it....). But shouldn't this be added as a patch to the current TW build sources? It is a clear bug in the boost files that might well hit more people.
(In reply to Peter Sütterlin from comment #4) > Yes, I added that line myself (in spsc_queue.hpp of boost, else I'd have to > 'fix' all packages using it....). > > But shouldn't this be added as a patch to the current TW build sources? It > is a clear bug in the boost files that might well hit more people. If boost upload becomes necessary before next version release, it will be added. Otherwise waiting for next boost version. Tumbleweed was rebuilt with new boost and there was no major problems.
(In reply to Adam Majer from comment #5) > Tumbleweed was rebuilt with > new boost and there was no major problems. Well, this does not mean it is without errors. It just suggests that none of the TW packages uses the lockfree module.....
Done with Boost 1.67.0. Now onto Boost 1.68.0 bugs in Bug 1105081