GNU bug report logs -
#57303
powerpc64le: rust build failure is bottleneck for many packages
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 57303 in the body.
You can then email your comments to 57303 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#57303
; Package
guix
.
(Fri, 19 Aug 2022 19:28:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Marcel van der Boom <marcel <at> van-der-boom.nl>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Fri, 19 Aug 2022 19:28:01 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
I use a Talos II machine as my daily driver and slowly migrating
as many packages to GUIX along the way. The kernel I am running
comes fromm https://archlinuxpower.org/
For many packages, rust is getting to be the bottleneck as a
dependency that does not build.
From what I can see there's a whole chain of rust dependencies
going back to rust <at> 1.39.0 which then ultimately fails with:
--8<---------------cut here---------------start------------->8---
(16/112) BUILDING bitflags v1.1.0
> /tmp/guix-build-rust-1.39.0.drv-0/mrustc/bin/mrustc
> rustc-1.39.0-src/vendor/bitflags/src/lib.rs -o
> output/rustc-build/libbitflags-1_1_0.rlib --crate-name bitflags
> --crate-type rlib -C
> emit-depfile=output/rustc-build/libbitflags-1_1_0.rlib.d
> --crate-tag 1_1_0 -g --cfg debug_assertions -O -L output -L
> output/rustc-build --cfg bitflags_const_fn
(17/112) BUILDING cc v1.0.35
> /tmp/guix-build-rust-1.39.0.drv-0/mrustc/bin/mrustc
> rustc-1.39.0-src/vendor/cc/src/lib.rs -o
> output/rustc-build/libcc-1_0_35.rlib --crate-name cc
> --crate-type rlib -C
> emit-depfile=output/rustc-build/libcc-1_0_35.rlib.d --crate-tag
> 1_0_35 -g --cfg debug_assertions -O -L output -L
> output/rustc-build
> /tmp/guix-build-rust-1.39.0.drv-0/mrustc/bin/mrustc
> rustc-1.39.0-src/src/librustc_llvm/build.rs --crate-name build
> --crate-type bin -o output/rustc-build/build_rustc_llvm_run -L
> output/rustc-build -g -L output --extern
> build_helper=output/rustc-build/libbuild_helper-0_1_0.rlib
> --extern cc=output/rustc-build/libcc-1_0_35.rlib --edition 2018
> /tmp/guix-build-rust-1.39.0.drv-0/mrustc/output/rustc-build/build_rustc_llvm_run
thread 'main' panicked at 'assertion failed: `(left == right)`
left: `1`,
right: `0`',
rustc-1.39.0-src/vendor/hashbrown/src/raw/mod.rs:1086:59
Process was terminated with signal 6
--8<---------------cut here---------------end--------------->8---
The line in =mod.rs= points to an assertion in some sort of table
iterator. Way over my head.
I know rust runs on powerpc64le because I have a binary version
1.62 installed through https://archlinuxpower.org/
Is anyone familiar with this working on rust on powerpc64 for the
powerpc64le-linux system?
Reply sent
to
Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
:
You have taken responsibility.
(Fri, 19 Aug 2022 20:13:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
Marcel van der Boom <marcel <at> van-der-boom.nl>
:
bug acknowledged by developer.
(Fri, 19 Aug 2022 20:13:02 GMT)
Full text and
rfc822 format available.
Message #10 received at 57303-done <at> debbugs.gnu.org (full text, mbox):
tags 57303 +notabug
thanks
Hi!
Marcel van der Boom <marcel <at> van-der-boom.nl> writes:
> I use a Talos II machine as my daily driver and slowly migrating
> as many packages to GUIX along the way. The kernel I am running
> comes fromm https://archlinuxpower.org/
Cool!
> For many packages, rust is getting to be the bottleneck as a
> dependency that does not build.
>
>>From what I can see there's a whole chain of rust dependencies
> going back to rust <at> 1.39.0 which then ultimately fails with:
>
> (16/112) BUILDING bitflags v1.1.0
>> /tmp/guix-build-rust-1.39.0.drv-0/mrustc/bin/mrustc
>> rustc-1.39.0-src/vendor/bitflags/src/lib.rs -o
>> output/rustc-build/libbitflags-1_1_0.rlib --crate-name bitflags
>> --crate-type rlib -C
>> emit-depfile=output/rustc-build/libbitflags-1_1_0.rlib.d
>> --crate-tag 1_1_0 -g --cfg debug_assertions -O -L output -L
>> output/rustc-build --cfg bitflags_const_fn
> (17/112) BUILDING cc v1.0.35
>> /tmp/guix-build-rust-1.39.0.drv-0/mrustc/bin/mrustc
>> rustc-1.39.0-src/vendor/cc/src/lib.rs -o
>> output/rustc-build/libcc-1_0_35.rlib --crate-name cc
>> --crate-type rlib -C
>> emit-depfile=output/rustc-build/libcc-1_0_35.rlib.d --crate-tag
>> 1_0_35 -g --cfg debug_assertions -O -L output -L
>> output/rustc-build
>> /tmp/guix-build-rust-1.39.0.drv-0/mrustc/bin/mrustc
>> rustc-1.39.0-src/src/librustc_llvm/build.rs --crate-name build
>> --crate-type bin -o output/rustc-build/build_rustc_llvm_run -L
>> output/rustc-build -g -L output --extern
>> build_helper=output/rustc-build/libbuild_helper-0_1_0.rlib
>> --extern cc=output/rustc-build/libcc-1_0_35.rlib --edition 2018
>> /tmp/guix-build-rust-1.39.0.drv-0/mrustc/output/rustc-build/build_rustc_llvm_run
> thread 'main' panicked at 'assertion failed: `(left == right)`
> left: `1`,
> right: `0`',
> rustc-1.39.0-src/vendor/hashbrown/src/raw/mod.rs:1086:59
> Process was terminated with signal 6
>
>
> The line in =mod.rs= points to an assertion in some sort of table
> iterator. Way over my head.
Working only on x86_64 is a limitation of mrustc, which is used to
bootstrap rust cleanly from sources on Guix.
> I know rust runs on powerpc64le because I have a binary version
> 1.62 installed through https://archlinuxpower.org/
Yes, Rust itself is not the problem, but its bootstrap.
I'd suggest lending a hand to mrustc to iron out issues like this or
request to Rust upstream support for bootstrapping for sources.
Investigating future alternatives such as GCC Rust or other similar
efforts could be useful for the time they are ripe to use, too.
Closing, as there's not much we can do on Guix's side.
Thanks,
Maxim
Information forwarded
to
bug-guix <at> gnu.org
:
bug#57303
; Package
guix
.
(Sat, 20 Aug 2022 08:08:02 GMT)
Full text and
rfc822 format available.
Message #13 received at 57303 <at> debbugs.gnu.org (full text, mbox):
For reference: this is the mrustc bug that needs resolving
https://github.com/thepowersgang/mrustc/issues/194
Information forwarded
to
bug-guix <at> gnu.org
:
bug#57303
; Package
guix
.
(Mon, 22 Aug 2022 08:58:01 GMT)
Full text and
rfc822 format available.
Message #16 received at 57303 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On Fri, Aug 19, 2022 at 08:56:10PM +0200, Marcel van der Boom wrote:
>
> I use a Talos II machine as my daily driver and slowly migrating as many
> packages to GUIX along the way. The kernel I am running comes fromm
> https://archlinuxpower.org/
>
>
> For many packages, rust is getting to be the bottleneck as a dependency that
> does not build.
>
> From what I can see there's a whole chain of rust dependencies going back to
> rust <at> 1.39.0 which then ultimately fails with:
>
>
> --8<---------------cut here---------------start------------->8---
> (16/112) BUILDING bitflags v1.1.0
> > /tmp/guix-build-rust-1.39.0.drv-0/mrustc/bin/mrustc
> > rustc-1.39.0-src/vendor/bitflags/src/lib.rs -o
> > output/rustc-build/libbitflags-1_1_0.rlib --crate-name bitflags
> > --crate-type rlib -C
> > emit-depfile=output/rustc-build/libbitflags-1_1_0.rlib.d --crate-tag
> > 1_1_0 -g --cfg debug_assertions -O -L output -L output/rustc-build --cfg
> > bitflags_const_fn
> (17/112) BUILDING cc v1.0.35
> > /tmp/guix-build-rust-1.39.0.drv-0/mrustc/bin/mrustc
> > rustc-1.39.0-src/vendor/cc/src/lib.rs -o
> > output/rustc-build/libcc-1_0_35.rlib --crate-name cc --crate-type rlib
> > -C emit-depfile=output/rustc-build/libcc-1_0_35.rlib.d --crate-tag
> > 1_0_35 -g --cfg debug_assertions -O -L output -L output/rustc-build
> > /tmp/guix-build-rust-1.39.0.drv-0/mrustc/bin/mrustc
> > rustc-1.39.0-src/src/librustc_llvm/build.rs --crate-name build
> > --crate-type bin -o output/rustc-build/build_rustc_llvm_run -L
> > output/rustc-build -g -L output --extern
> > build_helper=output/rustc-build/libbuild_helper-0_1_0.rlib --extern
> > cc=output/rustc-build/libcc-1_0_35.rlib --edition 2018
> > /tmp/guix-build-rust-1.39.0.drv-0/mrustc/output/rustc-build/build_rustc_llvm_run
> thread 'main' panicked at 'assertion failed: `(left == right)`
> left: `1`,
> right: `0`', rustc-1.39.0-src/vendor/hashbrown/src/raw/mod.rs:1086:59
> Process was terminated with signal 6
> --8<---------------cut here---------------end--------------->8---
>
>
> The line in =mod.rs= points to an assertion in some sort of table iterator.
> Way over my head.
>
> I know rust runs on powerpc64le because I have a binary version 1.62
> installed through https://archlinuxpower.org/
>
>
> Is anyone familiar with this working on rust on powerpc64 for the
> powerpc64le-linux system?
About 2 months ago I spent some time and got the rust bootstrap working
for riscv64-linux. I would suggest looking at the staging branch since
there the rust bootstrap version is at 1.54.
--
Efraim Flashner <efraim <at> flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#57303
; Package
guix
.
(Mon, 22 Aug 2022 09:09:02 GMT)
Full text and
rfc822 format available.
Message #19 received at 57303 <at> debbugs.gnu.org (full text, mbox):
[Efraim Flashner]:
>> Is anyone familiar with this working on rust on powerpc64 for
>> the
>> powerpc64le-linux system?
> About 2 months ago I spent some time and got the rust bootstrap
> working
> for riscv64-linux. I would suggest looking at the staging branch
> since
> there the rust bootstrap version is at 1.54.
Ah, I didn't even think of that, thanks! Will try that.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#57303
; Package
guix
.
(Tue, 23 Aug 2022 09:40:02 GMT)
Full text and
rfc822 format available.
Message #22 received at 57303 <at> debbugs.gnu.org (full text, mbox):
[Marcel van der Boom]:
> [Efraim Flashner]:
>> About 2 months ago I spent some time and got the rust bootstrap
>> working
>> for riscv64-linux. I would suggest looking at the staging
>> branch since
>> there the rust bootstrap version is at 1.54.
> Ah, I didn't even think of that, thanks! Will try that.
Unfortunately, it fails with the exact same error
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Tue, 20 Sep 2022 11:24:05 GMT)
Full text and
rfc822 format available.
This bug report was last modified 2 years and 275 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.