From: Thomas Wolff <towo@towo.net>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] cygwin 3.3.0-0.1.9814cfd8f693 (TEST)
Date: Sat, 18 Sep 2021 23:30:08 +0200 [thread overview]
Message-ID: <765b6a51-10eb-d801-cd66-6d457bf56748@towo.net> (raw)
In-Reply-To: <64c9fbd9-a370-ec24-a538-c0eed5b93341@cornell.edu>
Am 18.09.2021 um 22:20 schrieb Ken Brown via Cygwin:
> On 9/18/2021 4:01 PM, Denis Excoffier wrote:
>>> On 2021-09-17 22:33, Ken Brown via Cygwin-announce
>>> <cygwin-announce@cygwin.com> wrote:
>>>
>>> The following packages have been uploaded to the Cygwin distribution
>>> as test
>>> releases:
>>>
>>> * cygwin-3.3.0-0.1.9814cfd8f693
>>> * cygwin-devel-3.3.0-0.1.9814cfd8f693
>>> * cygwin-doc-3.3.0-0.1.9814cfd8f693
>>>
>>
>> Hello,
>>
>> It seems to me that the files Makefile.in, aclocal.m4, configure (and
>> the like) are missing from the folder (and sub-folders of)
>> newlib-cygwin/winsup
>> found within the
>> cygwin-3.3.0-0.1.9814cfd8f693.src/newlib-cygwin-3.3.0.tar.bz2 file
>> stored in cygwin-3.3.0-0.1.9814cfd8f693-src.tar.xz.
>
> The build now uses automake, and the missing files you refer to are
> all generated. Start by running winsup/autogen.sh.
This is a very bad idea (as I had commented before). There are too many
build system around already and now there's even a proprietary script to
run as a first step for cygwin. If there's anything useful that this
script accomplishes, why can't it just be invoked automatically from the
makefile or configure script so everything works as expected? It's a
gross violation of the principle of least surprise.
>
> Ken
>
next prev parent reply other threads:[~2021-09-18 21:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-17 20:33 Ken Brown via Cygwin-announce
2021-09-18 15:33 ` Achim Gratz
2021-09-18 19:03 ` Chris Roehrig
2021-09-18 20:17 ` Ken Brown
2021-09-18 20:01 ` Denis Excoffier
2021-09-18 20:20 ` Ken Brown
2021-09-18 21:30 ` Thomas Wolff [this message]
2021-09-18 22:32 ` Ken Brown
2021-09-19 0:49 ` Hans-Bernhard Bröker
2021-09-19 6:42 ` ASSI
2021-09-19 12:27 ` Ken Brown
2021-09-19 13:32 ` Thomas Wolff
2021-09-19 14:42 ` Ken Brown
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=765b6a51-10eb-d801-cd66-6d457bf56748@towo.net \
--to=towo@towo.net \
--cc=cygwin@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).