From: Eli Schwartz <eschwartz@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Fragile rust update is wedged. (Was: Fragile python update is wedged.)
Date: Fri, 2 May 2025 13:47:02 -0400 [thread overview]
Message-ID: <d75bba64-8e89-4fe2-8991-ede6f168a2a1@gentoo.org> (raw)
In-Reply-To: <aBT70LRzy1B9Awwt@MAC.fritz.box>
[-- Attachment #1.1: Type: text/plain, Size: 2025 bytes --]
On 5/2/25 1:07 PM, Alan Mackenzie wrote:
> Hello, Gentoo.
>
> I've just been trying the update for python 3.13. It went well on my
> new machine (well, after unmerging app-portage/unsymlink-lib, which was
> debris from some 2019 update).
>
> On my old machine, however, there was a seg fault while merging rust.
> This is a known problem in certain first generation Ryzen processors.
>
> However, this left the build wedged: emerge says that there's a circular
> dependency from rust to itself. More precisely, the error message looks
> like:
This is clearly not a python update, then.
> This would appear to be a bug in the rust ebuild - it has set itself as a
> builtime dependency before it had been built - or something like that.
>
> How do I best recover from this?
It is not a bug in the rust ebuild -- the rust ebuild has always,
always, always depended on itself. In the past, the rust ebuild silently
downloaded a temporary copy of dev-lang/rust-bin to work around this.
This was changed in November 2024.
The rust compiler is written in the rust programming language, using
bleeding-edge features of the most recent version of rust. They are
aware that this is a bootstrap problem and don't consider it a problem,
because rust is officially installed by downloading prebuilt binaries
into $HOME.
Compiling rust officially requires building the pre 1.0 version of rust,
itself written in ocaml, and then building *every* version of rust since
then, one by one, in turn, without skipping a single one. That is over
80 different versions of rust, you need to compile all of them in order
to get to the current one.
On amd64, you can use the unofficial dev-lang/mrustc (third-party
reimplementation of rust written in C++) which allows you to skip all
the way to rust 1.74, and from there it is "only" 13 or so versions to
build.
Or, you may use rust-bin. Alternatively, you may use:
```
emerge --getbinpkg dev-lang/rust
```
--
Eli Schwartz
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2025-05-02 17:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-02 17:07 [gentoo-user] Fragile python update is wedged Alan Mackenzie
2025-05-02 17:22 ` Pramod V U
2025-05-02 17:47 ` Eli Schwartz [this message]
2025-05-02 19:07 ` [gentoo-user] Fragile rust " Alan Mackenzie
2025-05-02 20:07 ` Eli Schwartz
2025-05-02 21:15 ` [gentoo-user] Fragile python update is wedged [Was: Fragile rust update is wedged] Alan Mackenzie
2025-05-02 21:35 ` Wol
2025-05-02 21:44 ` Jay Faulkner
2025-05-02 22:17 ` Alan Mackenzie
2025-05-02 22:21 ` Jay Faulkner
2025-05-02 21:56 ` Eli Schwartz
2025-05-04 16:41 ` Alan Mackenzie
2025-05-04 17:01 ` Eli Schwartz
2025-05-03 3:14 ` [gentoo-user] " Grant Edwards
2025-05-03 4:07 ` [gentoo-user] Fragile rust update is wedged Nate Eldredge
2025-05-11 11:54 ` [gentoo-user] Fragile python " Wol
2025-05-11 12:42 ` Dale
2025-05-11 13:26 ` Philip Webb
2025-05-11 14:52 ` Dale
2025-05-17 7:17 ` Dale
2025-05-18 12:06 ` Michael
2025-05-18 14:26 ` Dale
2025-05-11 15:14 ` Eli Schwartz
2025-05-11 12:43 ` Frank Schletz
2025-05-11 13:37 ` Wol
2025-05-11 14:55 ` Dale
2025-05-11 15:04 ` Eli Schwartz
2025-05-11 17:40 ` Wol
2025-05-11 18:06 ` Michael
2025-05-11 18:08 ` Eli Schwartz
2025-05-11 19:10 ` Wol
2025-05-11 19:47 ` Eli Schwartz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d75bba64-8e89-4fe2-8991-ede6f168a2a1@gentoo.org \
--to=eschwartz@gentoo.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox