Mailing List Archive

new installation - ERROR: dev-lang/rust-1.47.0-r2::gentoo failed (compile phase)
Reinstalling Gentoo on one box (I wiped the root partition, so it is a clean install) and I'm getting this error

* ERROR: dev-lang/rust-1.47.0-r2::gentoo failed (compile phase):
* (no error message)
*
* Call stack:
* ebuild.sh, line 125: Called src_compile
* environment, line 3644: Called die
* The specific snippet of code:
* env $(cat "${S}"/config.env) RUST_BACKTRACE=1 "${EPYTHON}" ./x.py dist -vv --config="${S}"/config.toml -j$(makeopts_jobs) || die )
*
* If you need support, post the output of `emerge --info '=dev-lang/rust-1.47.0-r2::gentoo'`,
* the complete build log and the output of `emerge -pqv '=dev-lang/rust-1.47.0-r2::gentoo'`.
* The complete build log is located at '/var/tmp/portage/dev-lang/rust-1.47.0-r2/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-lang/rust-1.47.0-r2/temp/environment'.
* Working directory: '/var/tmp/portage/dev-lang/rust-1.47.0-r2/work/rustc-1.47.0-src'
* S: '/var/tmp/portage/dev-lang/rust-1.47.0-r2/work/rustc-1.47.0-src'

tail /var/tmp/portage/dev-lang/rust-1.47.0-r2/temp/build.log

expected success, got: exit code: 101
< ToolBuild { compiler: Compiler { stage: 1, host: TargetSelection { triple: "x86_64-unknown-linux-gnu", file: None } }, target: TargetSelection { triple: "x86_64-unknown-linux-gnu", file: None }, tool: "rls", path: "src/tools/rls", mode: ToolRustc, is_optional_tool: true, source_type: Submodule, extra_features: ["clippy"] }
< Rls { compiler: Compiler { stage: 1, host: TargetSelection { triple: "x86_64-unknown-linux-gnu", file: None } }, target: TargetSelection { triple: "x86_64-unknown-linux-gnu", file: None }, extra_features: [] }
thread 'main' panicked at 'Unable to build RLS', src/bootstrap/dist.rs:66:9
stack backtrace:
0: backtrace::backtrace::libunwind::trace
at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.46/src/backtrace/libunwind.rs:86
1: backtrace::backtrace::trace_unsynchronized
at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.46/src/backtrace/mod.rs:66
2: std::sys_common::backtrace::_print_fmt
at src/libstd/sys_common/backtrace.rs:78
3: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
at src/libstd/sys_common/backtrace.rs:59
4: core::fmt::write
at src/libcore/fmt/mod.rs:1076
5: std::io::Write::write_fmt
at src/libstd/io/mod.rs:1537
6: std::sys_common::backtrace::_print
at src/libstd/sys_common/backtrace.rs:62
7: std::sys_common::backtrace::print
at src/libstd/sys_common/backtrace.rs:49
8: std::panicking::default_hook::{{closure}}
at src/libstd/panicking.rs:198
9: std::panicking::default_hook
at src/libstd/panicking.rs:217
10: std::panicking::rust_panic_with_hook
at src/libstd/panicking.rs:526
11: rust_begin_unwind
at src/libstd/panicking.rs:437
12: std::panicking::begin_panic_fmt
at src/libstd/panicking.rs:391
13: bootstrap::dist::missing_tool
at src/bootstrap/dist.rs:66
14: <bootstrap::dist::Rls as bootstrap::builder::Step>::run::{{closure}}
at src/bootstrap/dist.rs:1308
15: core::option::Option<T>::or_else
at /rustc/04488afe34512aa4c33566eb16d8c912a3ae04f9/src/libcore/option.rs:763
16: <bootstrap::dist::Rls as bootstrap::builder::Step>::run
at src/bootstrap/dist.rs:1305
17: bootstrap::builder::Builder::ensure
at src/bootstrap/builder.rs:1414
18: <bootstrap::dist::Extended as bootstrap::builder::Step>::run
at src/bootstrap/dist.rs:1763
19: bootstrap::builder::Builder::ensure
at src/bootstrap/builder.rs:1414
20: <bootstrap::dist::Extended as bootstrap::builder::Step>::make_run
at src/bootstrap/dist.rs:1745
21: bootstrap::builder::StepDescription::maybe_run
at src/bootstrap/builder.rs:189
22: bootstrap::builder::StepDescription::run
at src/bootstrap/builder.rs:211
23: bootstrap::builder::Builder::run_step_descriptions
at src/bootstrap/builder.rs:597
24: bootstrap::builder::Builder::execute_cli
at src/bootstrap/builder.rs:588
25: bootstrap::Build::build
at src/bootstrap/lib.rs:488
26: bootstrap::main
at src/bootstrap/bin/main.rs:15
27: std::rt::lang_start::{{closure}}
at /rustc/04488afe34512aa4c33566eb16d8c912a3ae04f9/src/libstd/rt.rs:67
28: std::rt::lang_start_internal::{{closure}}
at src/libstd/rt.rs:52
29: std::panicking::try::do_call
at src/libstd/panicking.rs:348
30: std::panicking::try
at src/libstd/panicking.rs:325
31: std::panic::catch_unwind
at src/libstd/panic.rs:394
32: std::rt::lang_start_internal
at src/libstd/rt.rs:51
33: std::rt::lang_start
at /rustc/04488afe34512aa4c33566eb16d8c912a3ae04f9/src/libstd/rt.rs:67
34: main
35: __libc_start_main
36: _start
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Traceback (most recent call last):
File "./x.py", line 11, in <module>
bootstrap.main()
File "/var/tmp/portage/dev-lang/rust-1.47.0-r2/work/rustc-1.47.0-src/src/bootstrap/bootstrap.py", line 1009, in main
bootstrap(help_triggered)
File "/var/tmp/portage/dev-lang/rust-1.47.0-r2/work/rustc-1.47.0-src/src/bootstrap/bootstrap.py", line 995, in bootstrap
run(args, env=env, verbose=build.verbose)
File "/var/tmp/portage/dev-lang/rust-1.47.0-r2/work/rustc-1.47.0-src/src/bootstrap/bootstrap.py", line 143, in run
raise RuntimeError(err)
RuntimeError: failed to run: /var/tmp/portage/dev-lang/rust-1.47.0-r2/work/rustc-1.47.0-src/build/bootstrap/debug/bootstrap dist -vv --config=/var/tmp/portage/dev-lang/rust-1.47.0-r2/work/rustc-1.47.0-src/config.toml -j8
* ERROR: dev-lang/rust-1.47.0-r2::gentoo failed (compile phase):
* (no error message)
*
* Call stack:
* ebuild.sh, line 125: Called src_compile
* environment, line 3644: Called die
* The specific snippet of code:
* env $(cat "${S}"/config.env) RUST_BACKTRACE=1 "${EPYTHON}" ./x.py dist -vv --config="${S}"/config.toml -j$(makeopts_jobs) || die )

--
Thelma
Re: new installation - ERROR: dev-lang/rust-1.47.0-r2::gentoo failed (compile phase) [ In reply to ]
On Saturday, 16 January 2021 20:59:17 GMT thelma@sys-concept.com wrote:
> Reinstalling Gentoo on one box (I wiped the root partition, so it is a clean
> install) and I'm getting this error

--->8

Have you thought of using rust-bin instead of rust? "emerge -1 rust-bin" It
saves prodigious amounts of compiling here. Of course, you can't do that if
you need to set particular USE flags.

There was a discussion here a month or two ago. Either rust or rust-bin will
satisfy virtual/rust.

--
Regards,
Peter.
Re: new installation - ERROR: dev-lang/rust-1.47.0-r2::gentoo failed (compile phase) [ In reply to ]
On Sunday, 17 January 2021 11:04:17 GMT Peter Humphrey wrote:
> On Saturday, 16 January 2021 20:59:17 GMT thelma@sys-concept.com wrote:
> > Reinstalling Gentoo on one box (I wiped the root partition, so it is a
> > clean install) and I'm getting this error
>
> --->8
>
> Have you thought of using rust-bin instead of rust? "emerge -1 rust-bin" It
> saves prodigious amounts of compiling here. Of course, you can't do that if
> you need to set particular USE flags.
>
> There was a discussion here a month or two ago. Either rust or rust-bin will
> satisfy virtual/rust.


Rust uses up tonnes of RAM in compiling, so unless enough RAM and perhaps SWAP
is available, it could fail. Increasing resources and/or reducing the make
job number should improve the situation.
Re: new installation - ERROR: dev-lang/rust-1.47.0-r2::gentoo failed (compile phase) [ In reply to ]
? 2021/1/17 ??7:18, Michael ??:
> On Sunday, 17 January 2021 11:04:17 GMT Peter Humphrey wrote:
>> On Saturday, 16 January 2021 20:59:17 GMT thelma@sys-concept.com wrote:
>>> Reinstalling Gentoo on one box (I wiped the root partition, so it is a
>>> clean install) and I'm getting this error
>> --->8
>>
>> Have you thought of using rust-bin instead of rust? "emerge -1 rust-bin" It
>> saves prodigious amounts of compiling here. Of course, you can't do that if
>> you need to set particular USE flags.
>>
>> There was a discussion here a month or two ago. Either rust or rust-bin will
>> satisfy virtual/rust.
>
> Rust uses up tonnes of RAM in compiling, so unless enough RAM and perhaps SWAP
> is available, it could fail. Increasing resources and/or reducing the make
> job number should improve the situation.
Agree with above, please try flag like "-j1" or give more swap space.
And compile Rust really take a while, made my old computer scream for
almost a day.
It is really a bad experience to use a poor computer to do what a heavy job.

--
bobwxc
F645 5C7A 08E8 A637 24C6 D59E 36E9 4EAB B53E 516B
Re: new installation - ERROR: dev-lang/rust-1.47.0-r2::gentoo failed (compile phase) [ In reply to ]
On 1/17/21 4:18 AM, Michael wrote:
> On Sunday, 17 January 2021 11:04:17 GMT Peter Humphrey wrote:
>> On Saturday, 16 January 2021 20:59:17 GMT thelma@sys-concept.com wrote:
>>> Reinstalling Gentoo on one box (I wiped the root partition, so it is a
>>> clean install) and I'm getting this error
>>
>> --->8
>>
>> Have you thought of using rust-bin instead of rust? "emerge -1 rust-bin" It
>> saves prodigious amounts of compiling here. Of course, you can't do that if
>> you need to set particular USE flags.
>>
>> There was a discussion here a month or two ago. Either rust or rust-bin will
>> satisfy virtual/rust.
>
>
> Rust uses up tonnes of RAM in compiling, so unless enough RAM and perhaps SWAP
> is available, it could fail. Increasing resources and/or reducing the make
> job number should improve the situation.

I think that might have been the case, I run emerge second time and it compiled just fine.
Maybe I will switch to "rust-bin", thanks for suggestion. Why do we need it, is it part of "system-bootstrap"?
Re: new installation - ERROR: dev-lang/rust-1.47.0-r2::gentoo failed (compile phase) [ In reply to ]
? 2021/1/18 ??1:48, thelma@sys-concept.com ??:
> On 1/17/21 4:18 AM, Michael wrote:
>> On Sunday, 17 January 2021 11:04:17 GMT Peter Humphrey wrote:
>>> On Saturday, 16 January 2021 20:59:17 GMT thelma@sys-concept.com wrote:
>>>> Reinstalling Gentoo on one box (I wiped the root partition, so it is a
>>>> clean install) and I'm getting this error
>>> --->8
>>>
>>> Have you thought of using rust-bin instead of rust? "emerge -1 rust-bin" It
>>> saves prodigious amounts of compiling here. Of course, you can't do that if
>>> you need to set particular USE flags.
>>>
>>> There was a discussion here a month or two ago. Either rust or rust-bin will
>>> satisfy virtual/rust.
>>
>> Rust uses up tonnes of RAM in compiling, so unless enough RAM and perhaps SWAP
>> is available, it could fail. Increasing resources and/or reducing the make
>> job number should improve the situation.
> I think that might have been the case, I run emerge second time and it compiled just fine.
> Maybe I will switch to "rust-bin", thanks for suggestion. Why do we need it, is it part of "system-bootstrap"?
>
Rust is a computer language, some software written in Rust need a Rust
compiler.
As I known, firefox is one.

--
bobwxc
F645 5C7A 08E8 A637 24C6 D59E 36E9 4EAB B53E 516B
Re: new installation - ERROR: dev-lang/rust-1.47.0-r2::gentoo failed (compile phase) [ In reply to ]
On Monday, 18 January 2021 07:44:33 GMT bobwxc wrote:

> > I think that might have been the case, I run emerge second time and it
> > compiled just fine. Maybe I will switch to "rust-bin", thanks for
> > suggestion. Why do we need it, is it part of "system-bootstrap"?
> Rust is a computer language, some software written in Rust need a Rust
> compiler.
> As I known, firefox is one.

Also, here, spidermonkey, cbindgen and librsvg.

--
Regards,
Peter.