Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 689042

Summary: app-office/gnucash-3.5 does not build against dev-libs/boost-1.70.0
Product: Gentoo Linux Reporter: Kenneth Miller <millerkenj>
Component: Current packagesAssignee: Aaron W. Swenson <titanofold>
Status: RESOLVED WORKSFORME    
Severity: normal    
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: build log from error
emerge --info

Description Kenneth Miller 2019-06-30 20:13:30 UTC
Created attachment 581570 [details]
build log from error

gnucash-3.5 will not build against boost-1.70.0, builds against boost-1.65.0

build log from error attached
Comment 1 Kenneth Miller 2019-06-30 20:14:03 UTC
Created attachment 581572 [details]
emerge --info
Comment 2 David Seifert gentoo-dev 2019-06-30 21:56:58 UTC
this seems like this age old boost::re_detail_107000::cpp_regex_traits issue. This is very likely an ABI issue (similar to wx and its dreadful reliance on GCC ABI) where boost and the revdep were built with different GCC versions. Could you try compiling boost 1.70 and the consuming package with the same GCC version?
Comment 4 Kenneth Miller 2019-07-01 20:16:52 UTC
Gnucash is built with gcc since the build fails with clang as the compiler, boost does build with clang. Rebuilt boost-1.70.0 using gcc as compiler and then gnucash-3.5 builds properly.
Comment 5 Christopher Frömmel 2019-07-02 17:10:20 UTC
Rebuilding boost (and all bdeps several times) didn't work to solve this for me.
Comment 6 Christopher Frömmel 2019-07-02 17:30:53 UTC
(In reply to Christopher Frömmel from comment #5)
> Rebuilding boost (and all bdeps several times) didn't work to solve this for
> me.

I don't know what was wrong and why, but gnucash was successfully compiled now :D
Sorry.
Comment 7 Aaron W. Swenson gentoo-dev 2020-03-28 19:55:13 UTC
I've been building Gnucash against Boost 1.72 for sometime now. I've never been able to reproduce the issue, and the reporter seems to have fixed it as a matter of course.