>>> Source configured. >>> Compiling source in /var/tmp/portage/sys-apps/exa-0.8.0/work/exa-0.8.0 ... /var/tmp/portage/sys-apps/exa-0.8.0/temp/environment: line 475: cargo: command not found * ERROR: sys-apps/exa-0.8.0::gentoo failed (compile phase): * cargo build failed * ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-desktop-plasma_libressl_20181109-050110 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.1 [2] x86_64-pc-linux-gnu-8.2.0 * Available Python interpreters, in order of preference: [1] python3.7 [2] python3.6 [3] python2.7 (fallback) [4] jython2.7 (fallback) Available Ruby profiles: [1] ruby23 (with Rubygems) [2] ruby24 (with Rubygems) [3] ruby25 (with Rubygems) * java-config: The following VMs are available for generation-2: *) IcedTea JDK 3.9.0 [icedtea-bin-8] Available Java Virtual Machines: [1] icedtea-bin-8 system-vm emerge -qpvO sys-apps/exa [ebuild N ] sys-apps/exa-0.8.0 USE="-debug"
Created attachment 555232 [details] emerge-info.txt
Created attachment 555234 [details] emerge-history.txt
Created attachment 555236 [details] environment
Created attachment 555238 [details] etc.portage.tbz2
Created attachment 555240 [details] sys-apps:exa-0.8.0:20181115-142425.log
Created attachment 555242 [details] temp.tbz2
probably you got caught by recent rust weirdness with improper softblockers, unconditional cargo, and non-working env-update. Thu Nov 15 10:23:40 2018 <<< dev-lang/rust-1.29.2 Thu Nov 15 10:23:47 2018 >>> dev-lang/rust-1.30.1-r1 Thu Nov 15 10:24:31 2018 <<< dev-lang/rust-bin-1.29.2 Thu Nov 15 10:24:39 2018 >>> dev-lang/rust-bin-1.30.1-r1 Thu Nov 15 10:24:47 2018 <<< dev-util/cargo-0.30.0 you emerged rust and rust-bin , the 1.30.1-r1 is supposed to be a fixed one with a proper softblocker. cargo should be there, eclass just fails to call it. It'll be cool if you could print also provide rust info, similar to info for gcc/ruby/python. I have no idea which rust was used, and what flags did it have. can you still get that info? /etc/env.d/rust* may help, emerge --info for rust and rust-bin as well. but I'm still sure this is related to recent rust ebuild changes.
In the mean while I run eselect rust update and I think , yes, this is a dup of the rust issues seen today. BTW I'll enhance the tinderox info script
thanks again for tinderbox, it's awesome! closing this for now. I usually rebuild all rust packages with every rust bump on at least 2 machines, so I'd probably catch if something went really wrong. but I only use non-binary versions of rust. tried to replicate by installing rust-bin and playing with eselect/env-update and simply can't reproduce. blame the rust bumps!
