From: "R. Diez" <rdiezmail-newlib@yahoo.de>
To: Matthew Joyce <matthew.joyce@embedded-brains.de>
Cc: Newlib <newlib@sourceware.org>
Subject: Re: Question about autoreconf to regenerate configuration files
Date: Fri, 21 Jan 2022 16:02:37 +0100 [thread overview]
Message-ID: <bb93e94d-c4b9-c298-658b-e10a1fedb764@yahoo.de> (raw)
In-Reply-To: <26fff1a3-7743-e0ce-f7a6-70b39a030118@embedded-brains.de>
> [...]
> but I have also unwittingly modified well over 100 files (numerous Makefile.in, aclocal.m4, and configure files).
> I'd like to understand: Is this expected or desirable? Should I not be using autoreconf for this?
This is another drawback of checking into the repository the files generated by the Autotools, see this e-mail:
require autoconf-2.69 exactly
Wed Jan 12 20:01:01 GMT 2022
https://sourceware.org/pipermail/newlib/2022/018866.html
See also the answer from Mike Frysinger about this problem:
require autoconf-2.69 exactly
Wed Jan 12 21:37:22 GMT 2022
https://sourceware.org/pipermail/newlib/2022/018867.html
Regards,
rdiez
next prev parent reply other threads:[~2022-01-21 15:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 12:32 Matthew Joyce
2022-01-21 13:44 ` Corinna Vinschen
2022-01-21 15:02 ` R. Diez [this message]
2022-01-21 15:37 ` Joel Sherrill
2022-01-21 16:09 ` R. Diez
2022-01-21 22:09 ` Mike Frysinger
2022-01-21 23:08 ` Joel Sherrill
2022-01-22 21:20 ` R. Diez
2022-01-23 0:17 ` Joel Sherrill
2022-01-23 16:57 ` R. Diez
2022-01-26 10:19 ` Mike Frysinger
2022-01-30 22:22 ` R. Diez
2022-01-23 7:29 ` Mike Frysinger
2022-01-26 10:02 ` Mike Frysinger
2022-02-17 5:18 ` Mike Frysinger
2022-02-17 6:56 ` Sebastian Huber
2022-02-20 9:51 ` R. Diez
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=bb93e94d-c4b9-c298-658b-e10a1fedb764@yahoo.de \
--to=rdiezmail-newlib@yahoo.de \
--cc=matthew.joyce@embedded-brains.de \
--cc=newlib@sourceware.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.
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).