>>> Install cargo-0.27.0 into /var/tmp/portage/dev-util/cargo-0.27.0/image/ category dev-util !!! dobin: target/release/cargo does not exist * ERROR: dev-util/cargo-0.27.0::gentoo failed (install phase): * dobin failed * ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 17.0-no-multilib-hardened_libressl_20180506-210133 ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-7.3.0 * Available Python interpreters, in order of preference: [1] python3.5 [2] python3.6 (fallback) [3] python2.7 (fallback) Available Ruby profiles: [1] ruby23 (with Rubygems) * emerge -qpv dev-util/cargo [ebuild N ] dev-util/cargo-0.27.0 USE="libressl -debug -doc"
Created attachment 531518 [details] emerge-info.txt
Created attachment 531520 [details] dev-util:cargo-0.27.0:20180515-013650.log
Created attachment 531522 [details] emerge-history.txt
Created attachment 531524 [details] environment
Created attachment 531526 [details] etc.portage.tbz2
Created attachment 531528 [details] logs.tbz2
Created attachment 531530 [details] temp.tbz2
I think this might be due to libressl. It would be good if you could check: - does the previous version build with libressl (cargo-0.26.0)? - does this version build correctly without libressl?
But it builds fine at another LibreSSL image: /home/tinderbox/run/17.0-developer_libressl_20180512-235059/var/log/emerge.log Tue May 15 13:55:16 2018 >>> dev-util/cargo-0.27.0 cargo: Tue May 15 13:42:53 2018: 12 minutes, 23 seconds cargo: 1 times
So it's got to have something to do with the hardened or no-multilib part? I'm happy to send a bug report upstream, but I think it needs to be a bit more targeted.
It fails due to LibreSSL 2.7.x isn't? Same as https://bugs.gentoo.org/655098 libgit2-sys 0.7.1 is still incompatible with LibreSSL 2.7.x.
Then I'm confused why it builds fine in Toralf's other libressl image.
Probably because the "other image" was using LibreSSL <= 2.6.x.
(In reply to Ian Moone from comment #13) Indeed: /home/tinderbox/run/17.0-developer_libressl_20180512-235059/var/log/emerge.log Sun May 13 04:15:46 2018 >>> dev-libs/libressl-2.6.4 libressl: Sun May 13 04:11:44 2018: 4 minutes, 2 seconds libressl: 1 times
(In reply to Ian Moone from comment #11) > It fails due to LibreSSL 2.7.x isn't? Same as https://bugs.gentoo.org/655098 > > libgit2-sys 0.7.1 is still incompatible with LibreSSL 2.7.x. Bug 655098 solves using libgit2-sys-0.7.3 as I have tested https://bugs.gentoo.org/655098#c16
We have the same error upgrading from cargo-0.28 to 0.29 !!! dobin: target/release/cargo does not exist * ERROR: dev-util/cargo-0.29.0::gentoo failed (install phase): * dobin failed on a system without libressl emerge -qpv dev-util/cargo [ebuild U ] dev-util/cargo-0.29.0 [0.28.0] USE="-debug -doc -libressl"
(In reply to Pierre-Yves Bonnetain-Nesterenko from comment #16) Take a look if you have rust-bin installed and selected: # eselect rust list Available Rust versions: [1] rust-1.28.0 [2] rust-bin-1.25.0 * Setting the default to rust-1.28.0 solved that problem for me: # eselect rust set 1
(In reply to Frank Hellmuth from comment #17) > (In reply to Pierre-Yves Bonnetain-Nesterenko from comment #16) > > Take a look if you have rust-bin installed and selected: > > # eselect rust list > Available Rust versions: > [1] rust-1.28.0 > [2] rust-bin-1.25.0 * > > Setting the default to rust-1.28.0 solved that problem for me: > > # eselect rust set 1 Thanks. It did the trick (a few weeks ago, I'm late in my thanks).
closing, as package is gone. dev-lang/rust supports libressl and ships cargo.