From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: gerd.moellmann@gmail.com, 68464@debbugs.gnu.org,
schwab@linux-m68k.org, pierre.techoueyres@free.fr
Subject: bug#68464: 30.0.50; autogen.sh creating modified files in build-aux with Autoconf 2.72
Date: Sun, 21 Jan 2024 11:56:08 +0200 [thread overview]
Message-ID: <83a5ozrow7.fsf@gnu.org> (raw)
In-Reply-To: <2cdc3032-6173-4a24-895d-f4c0c2722995@cs.ucla.edu> (message from Paul Eggert on Sat, 20 Jan 2024 16:51:06 -0800)
> Date: Sat, 20 Jan 2024 16:51:06 -0800
> Cc: schwab@linux-m68k.org, gerd.moellmann@gmail.com,
> 68464-done@debbugs.gnu.org, Pierre Téchoueyres
> <pierre.techoueyres@free.fr>
> From: Paul Eggert <eggert@cs.ucla.edu>
>
> Anyway, these two files (along with other Gnulib-derived files in the
> Emacs repository) are updated automatically by admin/merge-gnulib. Today
> I did such an update on the master branch, so config.guess and
> config.sub are now updated to their latest versions.
Thanks.
> I then reproduced the problem that Gerd mentioned. Gnulib's config.guess
> etc. tend to be more up-to-date, and anyway the Emacs build is more
> reproducible if we use the Emacs repository version of config.guess etc.
> (instead of whatever version the developer's Autoconf happens to have),
> so I installed the attached patch which fixed the problem for me.
And thanks.
prev parent reply other threads:[~2024-01-21 9:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 6:33 bug#68464: 30.0.50; autogen.sh creating modified files in build-aux with Autoconf 2.72 Gerd Möllmann
2024-01-15 13:01 ` Eli Zaretskii
2024-01-15 20:40 ` Pierre Téchoueyres
2024-01-15 21:10 ` Stefan Kangas
2024-01-15 21:13 ` Andreas Schwab
2024-01-16 3:30 ` Eli Zaretskii
2024-01-16 20:24 ` Pierre Téchoueyres
2024-01-20 9:55 ` Eli Zaretskii
2024-01-21 0:51 ` Paul Eggert
2024-01-21 6:53 ` Gerd Möllmann
2024-01-21 9:56 ` Eli Zaretskii [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83a5ozrow7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=68464@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=gerd.moellmann@gmail.com \
--cc=pierre.techoueyres@free.fr \
--cc=schwab@linux-m68k.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.