From: Ken Brown <kbrown@cornell.edu>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH] Use automake (v5)
Date: Tue, 27 Apr 2021 13:00:29 -0400 [thread overview]
Message-ID: <62ca4187-f798-38b3-f5dd-b3844b99fcf5@cornell.edu> (raw)
In-Reply-To: <dd2be414-edd1-5502-050a-ecaaa5920db5@cornell.edu>
On 4/27/2021 12:52 PM, Ken Brown wrote:
> On 4/27/2021 11:50 AM, Jon Turney wrote:
>> On 20/04/2021 21:13, Jon Turney wrote:
>>> For ease of reviewing, this patch doesn't contain changes to generated
>>> files which would be made by running ./autogen.sh.
>> I pushed this patch.
>>
>> If you have an existing build directory, while you might get away with
>> invoking 'make' at the top-level, I would recommend blowing it away and
>> configuring again.
>
> I'm confused about how the generated files are going to get regenerated when
> necessary. I see calls to autogen (which I guess is /usr/bin/autogen.exe from
> the autogen package) in the Makefiles, but I don't see any calls to autogen.sh.
> Is the latter no longer needed?
Oh, never mind. The Makefiles just call autoconf, etc., as needed.
Ken
next prev parent reply other threads:[~2021-04-27 17:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-20 20:13 Jon Turney
2021-04-20 20:15 ` Jon Turney
2021-04-21 16:40 ` Corinna Vinschen
2021-04-22 11:57 ` Corinna Vinschen
2021-04-26 15:03 ` Corinna Vinschen
2021-04-27 15:54 ` Jon Turney
2021-04-27 15:50 ` Jon Turney
2021-04-27 16:52 ` Ken Brown
2021-04-27 17:00 ` Ken Brown [this message]
2021-04-27 18:32 ` Jon Turney
2021-05-02 15:28 ` Jon Turney
2021-05-02 18:25 ` Brian Inglis
2021-05-03 10:40 ` Corinna Vinschen
2021-05-03 10:43 ` Corinna Vinschen
2021-05-04 18:12 ` Jon Turney
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=62ca4187-f798-38b3-f5dd-b3844b99fcf5@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-patches@cygwin.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).