From: Eli Zaretskii <eliz@gnu.org>
To: Philipp <p.stephani2@gmail.com>
Cc: emacs-devel@gnu.org, perry@piermont.com
Subject: Re: build modifies config.guess and config.sub
Date: Thu, 29 Jul 2021 09:06:23 +0300 [thread overview]
Message-ID: <83v94tslgg.fsf@gnu.org> (raw)
In-Reply-To: <A74F4FE9-5270-427B-88FF-00656AA27349@gmail.com> (message from Philipp on Wed, 28 Jul 2021 22:27:25 +0200)
> From: Philipp <p.stephani2@gmail.com>
> Date: Wed, 28 Jul 2021 22:27:25 +0200
> Cc: Emacs developers <emacs-devel@gnu.org>
>
> > Am 28.07.2021 um 22:17 schrieb Perry E. Metzger <perry@piermont.com>:
> >
> > Howdy, all!
> >
> > Whenever I do a "git status" after cleaning up after a build, I learn that the files
> >
> > build-aux/config.guess
> > build-aux/config.sub
> >
> > have been modified. It's easy enough to do a "git restore" on them, but should they should actually be checked in? I thought they were supplied by the autotools?
>
> This issue has been discussed earlier (https://lists.gnu.org/archive/html/emacs-devel/2021-05/msg00130.html), but without conclusion.
There was a conclusion, from my POV:
https://lists.gnu.org/archive/html/emacs-devel/2021-05/msg00187.html
To make it more clear, this is an Autoconf misfeature, and if someone
wants to report a bug, it should be reported to the Autoconf
developers; we here have nothing we can do about this kind of
"progress".
next prev parent reply other threads:[~2021-07-29 6:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-28 20:17 build modifies config.guess and config.sub Perry E. Metzger
2021-07-28 20:27 ` Philipp
2021-07-29 6:06 ` Eli Zaretskii [this message]
2021-07-29 23:11 ` Perry E. Metzger
2021-07-30 6:03 ` Eli Zaretskii
2021-07-30 13:48 ` Perry E. Metzger
2021-07-30 13:54 ` Eli Zaretskii
2021-07-30 18:35 ` Alan Third
2021-07-30 18:53 ` Eli Zaretskii
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83v94tslgg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=p.stephani2@gmail.com \
--cc=perry@piermont.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).