unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: builder@sourceware.org
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
	Aurelien Jarno <aurelien@aurel32.net>,
	 "Carlos O'Donell" <carlos@redhat.com>,
	Florian Weimer <fweimer@redhat.com>,
	 Samuel Thibault <samuel.thibault@ens-lyon.org>,
	Wilco Dijkstra <wilco.dijkstra@arm.com>,
	 caiyinyu <caiyinyu@loongson.cn>,
	GNU C Library <libc-alpha@sourceware.org>
Subject: Re: ☠ Buildbot (Sourceware): glibc-snapshots-trunk - failed compile (failure) (master)
Date: Thu, 25 Apr 2024 08:29:11 -0700	[thread overview]
Message-ID: <CAMe9rOqV2fHnA_k8PPSTGZDcOqzoc6j3Nj5To4Y3uGe+OCnLJQ@mail.gmail.com> (raw)
In-Reply-To: <20240425122141.E583C3846410@sourceware.org>

On Thu, Apr 25, 2024 at 5:21 AM <builder@sourceware.org> wrote:
>
> A new failure has been detected on builder glibc-snapshots-trunk while building glibc.
>
> Full details are available at:
>     https://builder.sourceware.org/buildbot/#/builders/264/builds/382
>
> Build state: failed compile (failure)
> Revision: 3a3a4497421422aa854c855cbe5110ca7d598ffc
> Worker: snapshots
> Build Reason: (unknown)
> Blamelist: Adhemerval Zanella <adhemerval.zanella@linaro.org>, Aurelien Jarno <aurelien@aurel32.net>, Carlos O'Donell <carlos@redhat.com>, Florian Weimer <fweimer@redhat.com>, H.J. Lu <hjl.tools@gmail.com>, Samuel Thibault <samuel.thibault@ens-lyon.org>, Wilco Dijkstra <wilco.dijkstra@arm.com>, caiyinyu <caiyinyu@loongson.cn>
>
> Steps:
>
> - 0: worker_preparation ( success )
>
> - 1: git checkout ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#/builders/264/builds/382/steps/1/logs/stdio
>
> - 2: rm -rf glibc-build ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#/builders/264/builds/382/steps/2/logs/stdio
>
> - 3: configure ( success )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#/builders/264/builds/382/steps/3/logs/stdio
>         - config.log: https://builder.sourceware.org/buildbot/#/builders/264/builds/382/steps/3/logs/config_log
>
> - 4: make dist ( failure )
>     Logs:
>         - stdio: https://builder.sourceware.org/buildbot/#/builders/264/builds/382/steps/4/logs/stdio
>

On Fedora 40, "make INSTALL" generates a slightly different INSTALL:

diff --git a/INSTALL b/INSTALL
index 2f2d12c335..1047585695 100644
--- a/INSTALL
+++ b/INSTALL
@@ -21,11 +21,11 @@ allows removing the whole build directory in case
an error occurs, which
 is the safest way to get a fresh start and should always be done.

    From your object directory, run the shell script ‘configure’ located
-at the top level of the source tree.  In the scenario above, you’d type

                            ^
+at the top level of the source tree.  In the scenario above, you'd type

                            ^

-- 
H.J.

       reply	other threads:[~2024-04-25 15:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240425122141.E583C3846410@sourceware.org>
2024-04-25 15:29 ` H.J. Lu [this message]
2024-04-25 15:37   ` ☠ Buildbot (Sourceware): glibc-snapshots-trunk - failed compile (failure) (master) Mark Wielaard
2024-04-25 23:25     ` Andreas K. Huettel
2024-04-26  9:53       ` Mark Wielaard
2024-04-26 10:22         ` Andreas K. Huettel
2024-04-26 11:26           ` Mark Wielaard

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAMe9rOqV2fHnA_k8PPSTGZDcOqzoc6j3Nj5To4Y3uGe+OCnLJQ@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=aurelien@aurel32.net \
    --cc=builder@sourceware.org \
    --cc=caiyinyu@loongson.cn \
    --cc=carlos@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=wilco.dijkstra@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).