From: Thomas Wolff <towo@towo.net>
To: cygwin-developers@cygwin.com
Subject: Re: cygwin build drops out
Date: Wed, 30 Jun 2021 23:17:33 +0200 [thread overview]
Message-ID: <d53a2c99-5a5b-cad5-8e60-419453f6cf10@towo.net> (raw)
In-Reply-To: <af657f6b-91e5-5409-5824-085fe3dec4d7@dronecode.org.uk>
Am 30.06.2021 um 19:48 schrieb Jon Turney:
> On 30/06/2021 17:59, 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.
>> A new attempt to `make` changes nothing, still no winsup made.
>
> You probably need to run the top-level configure *after* running
> autogen.sh.
That works, thanks. (Had to remove a bunch of "register" specifiers from
the sources...)
I hope, honestly, that it's not intended to stay that way. The autogen
should be called by configure implicitly.
Thomas
>
> The "how do I build cygwin" FAQ has been updated for these changes,
> but that update hasn't been published yet, as there hasn't been a
> release with these changes yet.
>
next prev parent reply other threads:[~2021-06-30 21:17 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
2021-06-30 17:48 ` Jon Turney
2021-06-30 21:17 ` Thomas Wolff [this message]
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=d53a2c99-5a5b-cad5-8e60-419453f6cf10@towo.net \
--to=towo@towo.net \
--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).