test/meck_tests.erl:19: export_all flag enabled - all functions will be exported Compiling test/meck_tests.erl failed: ERROR: eunit failed while processing /var/tmp/portage/dev-erlang/meck-0.8.4/work/meck-0.8.4: rebar_abort * ERROR: dev-erlang/meck-0.8.4::gentoo failed (test phase): * rebar -C test.config compile 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) emerge -qpv dev-erlang/meck [ebuild N ] dev-erlang/meck-0.8.4 USE="{test}"
Created attachment 525166 [details] emerge-info.txt
Created attachment 525168 [details] dev-erlang:meck-0.8.4:20180323-235740.log
Created attachment 525170 [details] emerge-history.txt
Created attachment 525172 [details] environment
Created attachment 525174 [details] etc.portage.tbz2
Created attachment 525176 [details] temp.tbz2
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.
