From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: coreutils refresh request (again)
Date: Wed, 10 Jun 2020 18:46:55 +0200 [thread overview]
Message-ID: <73a89e83-3496-b2fe-162b-2ff7c038c0dc@gmail.com> (raw)
In-Reply-To: <DM6PR09MB4043A2D88F847670BC44F4CBA5830@DM6PR09MB4043.namprd09.prod.outlook.com>
On 10.06.2020 18:21, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
>> https://cygwin.com/pipermail/cygwin/2020-June/245104.html
>
> Wow dude! I did not expect a whole sob story out of that simple reminder;
> I did not urge anybody to do it right away, yet I just mentioned that the package
> was way out of its release cycle. I think that the time it took you to write
> all that response was pretty much comparable to the time required to package
> the new coreutils:
>
> $ ./configure
> ...
> $ time make
> ...
> real 6m33.420s
> user 4m10.671s
> sys 1m53.034s
>
> (and it builds just out of the box, FYI)
>
but it is missing the patch used to adapt it to Cygwin.
The patch modifies 27 files and unfortunately does not applies
clean to latest upstream source.
The are at lest 3 points that need rewriting
next prev parent reply other threads:[~2020-06-10 16:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 16:21 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2020-06-10 16:46 ` Marco Atzeri [this message]
2020-06-10 21:26 ` Brian Inglis
-- strict thread matches above, loose matches on Subject: below --
2020-06-10 18:24 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2020-06-10 18:58 ` Marco Atzeri
2020-05-31 14:52 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2020-06-04 13:56 ` Brian Inglis
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=73a89e83-3496-b2fe-162b-2ff7c038c0dc@gmail.com \
--to=marco.atzeri@gmail.com \
--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).