From: Arthur Cohen <arthur.cohen@embecosm.com>
To: Mark Wielaard <mark@klomp.org>, Thomas Schwinge <tschwinge@baylibre.com>
Cc: gcc-rust@gcc.gnu.org
Subject: Re: ☠ Buildbot (Sourceware): gccrust - failed compile (failure) (master)
Date: Fri, 1 Mar 2024 11:24:00 +0100 [thread overview]
Message-ID: <1ed31164-aa49-410f-8177-4346e74c0263@embecosm.com> (raw)
In-Reply-To: <20240229202253.GB4502@gnu.wildebeest.org>
Hi both,
On 2/29/24 21:22, Mark Wielaard wrote:
> Hi,
>
> On Thu, Feb 29, 2024 at 09:00:13PM +0100, Thomas Schwinge wrote:
>> Three 'cargo' ('command not found') as well as
>> one 'rustc' ('error[E0658]: `let...else` statements are unstable')
>> errors:
>
> Yeah, I noticed those earlier, but oddly the tree became compilable
> again earlier today, then broke again?
>
> I think what needs to happen is have a config check for the minimum
> versions of cargo and rustc that are now needed for when configuring
> for --enable-languages=rust.
Yes - sorry about that. I will spend some time trying to make it nice
for the builders and users overall but I am currently trying to finish
the implementation of format_args!() in time for 14.1. So this will take
me a little bit of time.
>
> Then we need to see for which builder arches/distros those versions of
> cargo and rustc are available and install them there (and disable the
> builders for which there is no good version available).
That makes sense to me :) thanks
>
> Cheers,
>
> Mark
next prev parent reply other threads:[~2024-03-01 9:24 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-29 18:09 builder
2024-02-29 20:00 ` Thomas Schwinge
2024-02-29 20:22 ` Mark Wielaard
2024-02-29 22:08 ` Jakub Dupak
2024-03-01 10:22 ` Arthur Cohen
2024-03-01 10:24 ` Arthur Cohen [this message]
2024-03-02 19:57 ` Mark Wielaard
-- strict thread matches above, loose matches on Subject: below --
2024-04-16 9:03 builder
2024-04-16 8:59 builder
2024-03-26 18:44 builder
2024-03-25 12:49 builder
2024-03-25 12:47 builder
2024-03-25 10:00 builder
2024-03-12 17:12 builder
2024-03-12 13:02 builder
2024-02-29 18:25 builder
2024-02-29 20:01 ` Thomas Schwinge
2024-02-26 19:35 builder
2023-09-14 22:57 builder
2023-08-28 16:01 builder
2023-08-01 16:40 builder
2023-07-30 18:43 builder
2023-07-30 18:40 builder
2023-07-29 17:23 builder
2023-06-25 21:47 builder
2023-06-20 9:42 builder
2023-04-27 23:54 builder
2023-04-27 23:42 builder
2023-04-13 12:53 builder
2023-03-17 18:01 builder
2023-02-13 12:36 builder
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=1ed31164-aa49-410f-8177-4346e74c0263@embecosm.com \
--to=arthur.cohen@embecosm.com \
--cc=gcc-rust@gcc.gnu.org \
--cc=mark@klomp.org \
--cc=tschwinge@baylibre.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).