unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: "H.J. Lu" <hjl.tools@gmail.com>, libc-alpha@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>,
	Mark Wielaard <mark@klomp.org>
Subject: Re: ☠ Buildbot (Sourceware): glibc-snapshots-trunk - failed compile (failure) (master)
Date: Fri, 26 Apr 2024 10:25:23 +1100	[thread overview]
Message-ID: <1847582.8hzESeGDPO@noumea> (raw)
In-Reply-To: <0816db5c861a18390a74dae54c4d34525f3dee05.camel@klomp.org>

[-- Attachment #1: Type: text/plain, Size: 1844 bytes --]

> > 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
> > 
> >                             ^
> > 
> 
> I had to look 6 times till I saw the difference between the you’d and
> you'd :)
> 
> Does anybody know what (which package upgrade) exactly caused this? And
> what is "correct" in this case?

In general that's texinfo, and the equivalent change was introduced elsewhere in 
(from memory) 2.38. 

commit 84e93afc734a3c30e35ed2d21466a44259ac577e
Author: Paul Eggert <eggert@cs.ucla.edu>
Date:   Thu Jun 29 09:20:41 2023 -0700
    Switch to UTF-8 for INSTALL
    This makes it slightly easier to read, and these days
    everybody can read UTF-8.

Now for what changed precisely in Fedora 40 you'll have to ask someone else...


> Maybe we should just spell it out?
> "In the scenario above, you would type..."
> 
> Currently the snapshots are build using fedora-latest, which indeed
> just switched to Fedora 40. We could use a distro that updates less
> frequently, like debian-stable, if we don't want to be bothered by
> these faster moving distros.

Millenial youngsters and their fancy unicode... :o)

-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer 
(council, comrel, toolchain, base-system, perl, libreoffice)
https://wiki.gentoo.org/wiki/User:Dilfridge

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-04-25 23:26 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 [this message]
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=1847582.8hzESeGDPO@noumea \
    --to=dilfridge@gentoo.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=aurelien@aurel32.net \
    --cc=caiyinyu@loongson.cn \
    --cc=carlos@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=hjl.tools@gmail.com \
    --cc=libc-alpha@sourceware.org \
    --cc=mark@klomp.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).