Summary: | dev-lang/rust fails to install on arm: dobin: build/i686-unknown-linux-gnu/stage2/bin/rustc does not exist | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Chí-Thanh Christopher Nguyễn <chithanh> |
Component: | Current packages | Assignee: | Gentoo Rust Project <rust> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | dschridde+gentoobugs, herrtimson, tsmksubc |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 602440 | ||
Bug Blocks: | 609654 | ||
Attachments: | build.log.xz |
Description
Chí-Thanh Christopher Nguyễn
2017-08-31 13:15:22 UTC
I'm having almost the same problem trying to build it via crossdev (i.e. "i686-pc-linux-gnu-emerge --buildpkgonly dev-lang/rust"): Finished release [optimized] target(s) in 1364.29 secs Copying stage1 rustc from stage1 (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu / x86_64-unknown-linux-gnu) Copying stage2 std from stage1 (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu / x86_64-unknown-linux-gnu) Copying stage2 test from stage1 (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu / x86_64-unknown-linux-gnu) Copying stage2 rustc from stage1 (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu / x86_64-unknown-linux-gnu) Copying stage2 compiler (x86_64-unknown-linux-gnu) Build completed successfully in 1:33:07 >>> Source compiled. >>> Test phase [not enabled]: dev-lang/rust-1.19.0 >>> Install rust-1.19.0 into /usr/i686-pc-linux-gnu/tmp/portage/dev-lang/rust-1.19.0/image/ category dev-lang !!! dobin: build/i686-unknown-linux-gnu/stage2/bin/rustc does not exist !!! dobin: build/i686-unknown-linux-gnu/stage2/bin/rustdoc does not exist There seem to be two separate problems here - rust's build system ignores cross compilation (it always builds for the host target), and the ebuild uses hardcoded platform triples (causing the dobin error). Can you try this with a recent 1.26 version? Support for arm should be much better now. Going to call this fixed, please reopen if you still see issues. |