Building libcaca@0.99.beta19_6+x11 on a PPC fails unless cppunit compiled with GCC6

[josephsacco]

If cppunit is installed and was compiled with GCC4.2, building libcaca will fail in the test directory on a PPC, due to missing symbols for PPC in cppunit.

The Portfile for libcaca contains the line

   PortGroup           cxx11 1.1

which will force the libcaca build to use GCC6 on a PPC. If cppunit is installed and was compiled with GCC4.2, the libcaca build will fail in the test directory due to missing symbols for PPC.

Recompiling cppunit with GCC6 fixes the problem. Someone who knows a lot more about Portfiles than I do could probably force the recompilation of cppunit from within the libcaca Portfile.

-Joseph

[kencu (Ken)]

but cppunit is also in the cxx11 1.1 portgroup, so it should never compile with gcc42, and this should have happened for you behind the scenes. Perhaps cppunit needs a revbump? Defer to michael here.

[ryandesign (Ryan Carsten Schmidt)]

libcaca was revbumped when the cxx11 1.1 portgroup was added to it in [fd96fbcd6861e6bca2bb6233cdd7291a4f2aeb87/macports-ports] on July 1.

But all ports that use the cxx11 1.1 portgroup were not revbumped when that portgroup was changed to use gcc6 on PowerPC in [1dab0d51d17febdd682ff263502055df81e31b0e/macports-ports] on July 3.

Prior to July 3, clang 4.0 would have been used. Does clang-4.0 work on PowerPC? If not, then the portgroup change doesn't need ports using the portgroup to be revbumped.

I agree, it doesn't look like there's a way that the current revision of the port could have been compiled with applegcc42.

[kencu (Ken)]

clang-4.0 does not work on PPC at present - the cxx11 portgroup was ignored on ppc until just very recently. So that would be it, I guess. Revbumping the whole group that uses cxx11 seems a bit aggressive.

Perhaps this is a one-off rare event for this combination of ports (IIUC, cppunit could build with gcc42, but it needs to build with cxx11-compatible gcc6 now to work with libcaca -- a bit of a weird situation).

Can we force a rebuild of the cppunit binary on the buildbot to make sure it's built with cxx11, and see if this comes up any further do you think, rather than revbumping 100+ ports for this?

[michaelld (Michael Dickens)]

In the interim between now & the prior comment, we've added to the cppunit port the requirement for cxx11 PortGroup, as well as fixed up GCC5 and GCC6 PPC to provide a c++11 compiler. Hence, I believe this ticket's issue is no longer relevant & I'm closing the ticket as fixed. If anyone objects, please reopen and post what's going on & why the ticket is still relevant.