Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 620934 - app-text/podofo-0.9.6_pre20170508-r1: build failing with cppunit-1.14.0 and gcc-5.4.0 (but not with gcc-6.3.0)
Summary: app-text/podofo-0.9.6_pre20170508-r1: build failing with cppunit-1.14.0 and g...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Zac Medico
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 637042
  Show dependency tree
 
Reported: 2017-06-05 16:14 UTC by rypervenche
Modified: 2017-11-10 12:47 UTC (History)
5 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
build.log (build.log,191.73 KB, text/x-log)
2017-06-05 16:14 UTC, rypervenche
Details
emerge -pv podofo and emerge --info (info.log,6.27 KB, text/plain)
2017-06-05 16:15 UTC, rypervenche
Details
The ebuild patch needed (podofo-0.9.6_pre20170508-r1.ebuild.patch,414 bytes, patch)
2017-06-05 18:00 UTC, PhobosK
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description rypervenche 2017-06-05 16:14:27 UTC
Created attachment 475270 [details]
build.log

When doing a normal emerge -avuND --with-bdeps y @world, I am unable to get podofo to rebuild. I have attached the build.log, my emerge --info, and emerge -pv podofo as attachments. I do see the reference to C++2011. I'm not sure if this has to do with the move to GCC5. I did run the revdep-rebuild command from eselect news and it recompiled a ton of packages, so I don't think it would be that.

Any help would be appreciated. Thank you!
Comment 1 rypervenche 2017-06-05 16:15:03 UTC
Created attachment 475272 [details]
emerge -pv podofo and emerge --info
Comment 2 Ben Kohler gentoo-dev 2017-06-05 16:23:20 UTC
The error suggests that cppunit didn't get rebuilt yet, can you try this command to see when it was last successfully built?

date -d @$(</var/db/pkg/dev-util/cppunit-*/BUILD_TIME)
Comment 3 Yoann Colin 2017-06-05 17:32:51 UTC
% date -d @$(</var/db/pkg/dev-util/cppunit-1.14.0/BUILD_TIME)
Sun May 28 10:51:14 CEST 2017
Comment 4 Yoann Colin 2017-06-05 17:36:10 UTC
After your question, I have rebuilt cppunit then podofo, but it failed again
Comment 5 PhobosK 2017-06-05 18:00:36 UTC
Created attachment 475286 [details, diff]
The ebuild patch needed

The problem is not in rebuilding... Its the podofo ebuild that needs updating...

The new dev-util/cppunit-1.14.0 requires when used, the -std=c++11 or -std=gnu++11 flags to be added in the application using it...

The error is a kinda self-explanatory:

------ skip -----
from /dev/shm/portage/app-text/podofo-0.9.6_pre20170508-r1/work/podofo-0.9.6_pre20170508/test/unit/ColorTest.cpp:21:
/usr/lib/gcc/x86_64-pc-linux-gnu/5.4.0/include/g++-v5/bits/c++0x_warning.h:32:2: error: #error This file requires compiler and library support for the ISO C++ 2011 standard. This support must be enabled with the -std=c++11 or -std=gnu++11 compiler options.
 #error This file requires compiler and library support \
  ^
In file included from /usr/include/cppunit/TestAssert.h:8:0
------ skip -----

So since podofo already inherits flag-o-matic, what's needed is to add:
 append-cxxflags "-std=c++11"

in src_prepare() or src_configure() stages of the ebuild....

BTW the same problem exists in  media-video/dirac-1.0.2-r1
Comment 6 Zac Medico gentoo-dev 2017-06-10 19:37:38 UTC
I can reproduce the problem with gcc-5.4.0, but not with gcc-6.3.0.

(In reply to PhobosK from comment #5)
> The new dev-util/cppunit-1.14.0 requires when used, the -std=c++11 or
> -std=gnu++11 flags to be added in the application using it...

Why is that necessary, when according to this news item, gcc-5 uses the new C++11 ABI by default?

https://www.gentoo.org/support/news-items/2015-10-22-gcc-5-new-c++11-abi.html

Anyway, I've pushed this fix which appears to suppress the problem when you don't have tests enabled:

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=24598d33ad2f2c5f9c2077ad850fb7516f782bdd
Comment 7 Andreas Sturmlechner gentoo-dev 2017-11-10 11:30:02 UTC
So, can we declare this solved?