From: Ben RUBSON <ben.rubson@gmx.com>
To: Cygwin Apps <cygwin-apps@cygwin.com>
Cc: Wayne Davison <wayne@opencoder.net>
Subject: Re: [ITP] xxhash 0.7.4-1
Date: Tue, 14 Jul 2020 23:57:16 +0200 [thread overview]
Message-ID: <EC11F007-BC5C-4851-A9E2-0207A266AD71@gmx.com> (raw)
In-Reply-To: <CAJ1FpuNxKZod0Qbu2EeX2pgvrBNqwf8haLmW7C9bm1bCQndYVA@mail.gmail.com>
> On 14 Jul 2020, at 21:51, Doug Henderson via Cygwin-apps <cygwin-apps@cygwin.com> wrote:
>
> On Tue, 14 Jul 2020 at 10:29, ASSI <> wrote:
>>
>> ASSI writes:
>>> By patching the Makefile, just like you need to do for all the other
>>> stuff from the same author. You can have a look at the zstd packages.
>>
>> Come to think of it, xxhash is already part of zstd. Can't you just
>> link to that?
>>
>>
>> Regards,
>> Achim.
>
> I have patched the Makefile as suggested. The newest version of the
> dist files as located at
>
> https://github.com/djhenderson/Temp/raw/master/xxhash.zip
>
> (...)
>
> Any way, I would like some critical feedback on the dist packaging.
Many thanks Doug, really nice work !
At least I successfully manage to build rsync with this package :
$ uname -s -r
CYGWIN_NT-6.1 3.1.6(0.340/5/3)
$ ./rsync --version
rsync version 3.2.3dev protocol version 31
(...)
Optimizations:
no SIMD, asm, openssl-crypto
Checksum list:
xxh64 (xxhash) md5 md4 none
Compress list:
zstd lz4 zlibx zlib none
Not sure about the other things to check though.
Kind regards,
Ben
next prev parent reply other threads:[~2020-07-14 21:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 22:09 Doug Henderson
2020-07-14 4:42 ` ASSI
2020-07-14 16:29 ` ASSI
2020-07-14 19:51 ` Doug Henderson
2020-07-14 21:57 ` Ben RUBSON [this message]
2020-08-02 10:41 ` Ben RUBSON
2020-08-03 3:36 ` Doug Henderson
2020-08-03 5:58 ` Marco Atzeri
2020-08-03 16:08 ` Marco Atzeri
2020-08-25 15:46 ` Ben RUBSON
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=EC11F007-BC5C-4851-A9E2-0207A266AD71@gmx.com \
--to=ben.rubson@gmx.com \
--cc=cygwin-apps@cygwin.com \
--cc=wayne@opencoder.net \
/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).