From: James Le Cuirot <chewi@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH 2/3] dev-lang/rust{,-bin}: Add 1.54.0
Date: Mon, 25 Nov 2024 22:31:11 +0000 [thread overview]
Message-ID: <88b93470a029d0b6ae29b21f076243ecf6cfa690.camel@gentoo.org> (raw)
In-Reply-To: <3004e82f-122c-4589-b93a-d94455573400@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 921 bytes --]
On Tue, 2024-11-26 at 07:36 +1000, Matt Jolly wrote:
> Hi,
>
> On 26/11/24 06:13, James Le Cuirot wrote:
>
> > You've lost some lines at the start of dev-lang/rust's src_configure, the
> > filter-lto line and the cross-compiler lines I added the other day. Was that
> > intentional?
>
> This ebuild was modified from 1.54.0 as it was when it was removed from
> the tree, and this branch didn't include those updates until a rebase
> before pushing.
>
> This is mostly intended to be a the beginnings of a 'binary-Rust-less'
> bootstrap path using `mrustc`, I can't really see any situation where
> the ability to cross-compile a very old rust adds value.
>
> I'll take some time today to implement, regardless.
Ah sorry, ignore me then! I wasn't paying attention and thought this was a new
version. There's a fair chance it won't cross-compile anyway, especially if an
older LLVM is involved.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 858 bytes --]
next prev parent reply other threads:[~2024-11-25 22:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 3:35 [gentoo-dev] [PATCH 0/3] cargo.eclass: Trivial crate replacements kangie
2024-11-25 3:35 ` [gentoo-dev] [PATCH 1/3] cargo.eclass: add trivial crate overrides kangie
2024-11-25 3:35 ` [gentoo-dev] [PATCH 2/3] dev-lang/rust{,-bin}: Add 1.54.0 kangie
2024-11-25 20:13 ` James Le Cuirot
2024-11-25 21:36 ` Matt Jolly
2024-11-25 22:31 ` James Le Cuirot [this message]
2024-11-25 3:35 ` [gentoo-dev] [PATCH 3/3] app-antivirus/clamav: example of trivial crate replacement kangie
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=88b93470a029d0b6ae29b21f076243ecf6cfa690.camel@gentoo.org \
--to=chewi@gentoo.org \
--cc=gentoo-dev@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