From: Thomas Schwinge <tschwinge@baylibre.com>
To: builder@sourceware.org,
Pierre-Emmanuel Patry <pierre-emmanuel.patry@embecosm.com>,
gcc-rust@gcc.gnu.org, Mark Wielaard <mark@klomp.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
Tamar Christina <tamar.christina@arm.com>,
Arthur Cohen <arthur.cohen@embecosm.com>
Subject: Re: ☠ Buildbot (Sourceware): gcc - failed configure (failure) (master)
Date: Mon, 15 Apr 2024 13:57:45 +0200 [thread overview]
Message-ID: <871q76n8hy.fsf@euler.schwinge.ddns.net> (raw)
In-Reply-To: <20240415115055.E391E384AB60@sourceware.org>
Hi!
On 2024-04-15T11:50:55+0000, builder@sourceware.org wrote:
> A new failure has been detected on builder gcc-fedora-mingw while building gcc.
>
> Full details are available at:
> https://builder.sourceware.org/buildbot/#/builders/262/builds/5337
>
> Build state: failed configure (failure)
As expected, a number of GCC builders are going to pass out after
GCC commit 3e1e73fc99584440e5967577f2049573eeaf4596
"build: Check for cargo when building rust language".
If I remember correctly, Mark said to look either into installing
suitable Cargo packages, or disable '--enable-languages=rust' for those.
Grüße
Thomas
> Revision: a3281dd0f4b46c16ec1192ad411c0a96e6d086eb
> Worker: bb1-1
> Build Reason: (unknown)
> Blamelist: H.J. Lu <hjl.tools@gmail.com>, Pierre-Emmanuel Patry <pierre-emmanuel.patry@embecosm.com>, Tamar Christina <tamar.christina@arm.com>, Thomas Schwinge <tschwinge@baylibre.com>
>
> Steps:
>
> - 0: worker_preparation ( success )
>
> - 1: git checkout ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#/builders/262/builds/5337/steps/1/logs/stdio
>
> - 2: rm -rf gcc-build ( success )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#/builders/262/builds/5337/steps/2/logs/stdio
>
> - 3: configure ( failure )
> Logs:
> - stdio: https://builder.sourceware.org/buildbot/#/builders/262/builds/5337/steps/3/logs/stdio
> - config.log: https://builder.sourceware.org/buildbot/#/builders/262/builds/5337/steps/3/logs/config_log
parent reply other threads:[~2024-04-15 11:57 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20240415115055.E391E384AB60@sourceware.org>]
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=871q76n8hy.fsf@euler.schwinge.ddns.net \
--to=tschwinge@baylibre.com \
--cc=arthur.cohen@embecosm.com \
--cc=builder@sourceware.org \
--cc=gcc-rust@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
--cc=mark@klomp.org \
--cc=pierre-emmanuel.patry@embecosm.com \
--cc=tamar.christina@arm.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).