src/riak_pb_codec.erl:33: export_all flag enabled - all functions will be exported Compiling src/riak_pb_codec.erl failed: ERROR: eunit failed while processing /var/tmp/portage/dev-erlang/riak_pb-2.2.0.2/work/riak_pb-2.2.0.2: rebar_abort * ERROR: dev-erlang/riak_pb-2.2.0.2::gentoo failed (test phase): * rebar eunit failed * ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-hardened_test_20180322-194027 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-5.4.0 * [2] x86_64-pc-linux-gnu-5.4.0-hardenednopie [3] x86_64-pc-linux-gnu-5.4.0-hardenednopiessp [4] x86_64-pc-linux-gnu-5.4.0-hardenednossp [5] x86_64-pc-linux-gnu-5.4.0-vanilla Available Python interpreters, in order of preference: [1] python3.5 [2] python3.6 (fallback) [3] python2.7 (fallback) [4] pypy3 (fallback) emerge -qpv dev-erlang/riak_pb [ebuild N ] dev-erlang/riak_pb-2.2.0.2
Created attachment 525416 [details] emerge-info.txt
Created attachment 525418 [details] dev-erlang:riak_pb-2.2.0.2:20180325-165721.log
Created attachment 525420 [details] emerge-history.txt
Created attachment 525422 [details] environment
Created attachment 525424 [details] etc.portage.tbz2
Created attachment 525426 [details] temp.tbz2
Created attachment 548780 [details] build.log (ppc) Identical test failure on ppc.
Not related to GCC 5
I believe this and all similar bugs should be covered by the subslot changes to the rebar eclass that should make sure we always rebuild for the right erlang version.