From: Mark Wielaard <mark@klomp.org>
To: "Andreas K. Huettel" <dilfridge@gentoo.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
libc-alpha@sourceware.org,
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>
Subject: Re: ☠ Buildbot (Sourceware): glibc-snapshots-trunk - failed compile (failure) (master)
Date: Fri, 26 Apr 2024 13:26:58 +0200 [thread overview]
Message-ID: <5850d5450cb2ca4efbe1ec8f0ab5f7f90c12cb7f.camel@klomp.org> (raw)
In-Reply-To: <7809733.lvqk35OSZv@noumea>
Hi Andreas,
On Fri, 2024-04-26 at 21:22 +1100, Andreas K. Huettel wrote:
> >
> > Maybe the simplest "solution" is turning --disable-encoding back on?
> > At least that seems to generate the same (boring ASCII only) INSTALL
> > file with both 7.0.3 and 7.1.
>
> Alternatively, we regenerate to 7.1 and call it the new baseline...
>
> [[I just checked and in Gentoo we even only have 7.1 left at the moment
> (though restoring the old version would be easy).]]
That works for me. The snapshot builder obviously (now) uses 7.1
already. And it would only really affect any release manager. Do we
have a page documenting the version of tools needed to make dist?
> Whatever we do with unicode will lead to failed checks somewhere then
> though.
Right. So we could also just decide the tools aren't really ready for
the new shiny unicode world yet and reintroduce --disable-encoding for
now and try again in a year or two for the INSTALL file.
Cheers,
Mark
prev parent reply other threads:[~2024-04-26 11:27 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 ` ☠ Buildbot (Sourceware): glibc-snapshots-trunk - failed compile (failure) (master) H.J. Lu
2024-04-25 15:37 ` 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 [this message]
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=5850d5450cb2ca4efbe1ec8f0ab5f7f90c12cb7f.camel@klomp.org \
--to=mark@klomp.org \
--cc=adhemerval.zanella@linaro.org \
--cc=aurelien@aurel32.net \
--cc=caiyinyu@loongson.cn \
--cc=carlos@redhat.com \
--cc=dilfridge@gentoo.org \
--cc=fweimer@redhat.com \
--cc=hjl.tools@gmail.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).