Compiled src/meck.erl src/meck_code_gen.erl:185: erlang:get_stacktrace/0: deprecated; use the new try/catch syntax for retrieving the stack backtrace Compiling src/meck_code_gen.erl failed: ERROR: compile 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 (compile phase): * rebar compile failed ------------------------------------------------------------------- This is an stable amd64 chroot image at a tinderbox (==build bot) name: 17.0-systemd_stable-libressl_20190503-232230 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-8.3.0 * Available Python interpreters, in order of preference: [1] python3.6 [2] python2.7 (fallback) Available Ruby profiles: [1] ruby24 (with Rubygems) * Available Rust versions: [1] rust-1.29.1 * java-config: The following VMs are available for generation-2: emerge -qpvO dev-erlang/meck [ebuild N ] dev-erlang/meck-0.8.4 USE="-test"
Created attachment 575730 [details] emerge-info.txt
Created attachment 575732 [details] dev-erlang:meck-0.8.4:20190506-230704.log
Created attachment 575734 [details] emerge-history.txt
Created attachment 575736 [details] environment
Created attachment 575738 [details] etc.portage.tbz2
Created attachment 575740 [details] temp.tbz2
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.