From: Ken Brown <kbrown@cornell.edu>
To: cygwin-developers@cygwin.com
Subject: Re: cygwin build drops out
Date: Wed, 30 Jun 2021 13:41:28 -0400 [thread overview]
Message-ID: <207c1678-bf73-b232-0222-e1e5ea01c65a@cornell.edu> (raw)
In-Reply-To: <13fb8d63-9421-08e6-39a1-b32827e0e303@towo.net>
On 6/30/2021 12:59 PM, Thomas Wolff wrote:
>
>
> Am 30.06.2021 um 18:07 schrieb Ken Brown:
>> On 6/30/2021 10:39 AM, Thomas Wolff wrote:
>>> Hi, recently I cannot build cygwin anymore.
>>> With a fresh git checkout, configure and make builds the newlib tree, no
>>> errors, but no winsup tree is built.
>>> Any similar problem or known current issue?
>>
>> This might be because of the recent switch to automake. You have to run
>> winsup/autogen.sh?
>>
>> Ken
> It says
> parallel-tests: installing '../test-driver'
> and terminates after a few seconds.
That's expected.
> A new attempt to `make` changes nothing, still no winsup made.
Did you run 'configure' before 'make'?
Ken
next prev parent reply other threads:[~2021-06-30 17:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 14:39 Thomas Wolff
2021-06-30 16:07 ` Ken Brown
2021-06-30 16:59 ` Thomas Wolff
2021-06-30 17:41 ` Ken Brown [this message]
2021-06-30 17:48 ` Jon Turney
2021-06-30 21:17 ` Thomas Wolff
2021-06-30 20:10 ` Mark Geisert
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=207c1678-bf73-b232-0222-e1e5ea01c65a@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-developers@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).