public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Chad Dougherty <crd@acm.org>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [ITP] rsync 3.2.6
Date: Thu, 6 Oct 2022 14:20:34 -0400	[thread overview]
Message-ID: <0a7633f3-f5ed-b436-6b5f-d7adbf9d37ba@acm.org> (raw)
In-Reply-To: <20221006172431.x74omlu2as5m2lcz@lucy.dinwoodie.org>

On 2022-10-06 13:24, Adam Dinwoodie wrote:
> "no iconv" concerns me; I'm not desperately familiar with how iconv
> works, but I believe that'll potentially cause issues for rsync users
> who aren't using ASCII.  I'd guess the issue is your build environment
> is missing a relevant build-time dependency, probably libiconv or
> libiconv-devel.
> 

Yeah, come to think of it that one also stuck out to me after I sent the 
mail.  I've updated my cygport and associated artifacts to include those 
dependencies:
https://github.com/crd477/cygports/tree/main/rsync

Here's an update diff of the features and capabilities, reformatted and 
sorted for easier comparison:
crd@x13:~/src/cygports/rsync$ diff -b old.txt new.txt
1,2c1,2
< rsync  version 3.2.4dev  protocol version 31
< Copyright (C) 1996-2020 by Andrew Tridgell, Wayne Davison, and others.
---
 > rsync  version 3.2.6  protocol version 31
 > Copyright (C) 1996-2022 by Andrew Tridgell, Wayne Davison, and others.
13a14,15
 >  crtimes
 >  hardlink-symlinks
17d18
<  no crtimes
19c20
<  optional protect-args
---
 >  optional secluded-args
27,28c28,30
<  no SIMD
<  asm
---
 >  no SIMD-roll
 >  no asm-MD5
 >  no asm-roll

I think the diffs after "19c20" above should be safe to ignore as the 
release notes explain them:
" - Renamed configure's `--enable-simd` option to `--enable-roll-simd` 
and added
    the option `--enable-roll-asm` to use the new asm version of the 
code.  Both
    are x86_64/amd64 only.

  - Renamed configure's `--enable-asm` option to `--enable-md5-asm` to avoid
    confusion with the asm option for the rolling checksum.  It is also 
honored
    even when openssl crypto is in use.  This allows: normal MD4 & MD5, 
normal
    MD4 + asm MD5, openssl MD4 & MD5, or openssl MD4 + asm MD5 depending 
on the
    configure options selected.

  - Made SIMD & asm configure checks default to "no" on non-Linux hosts 
due to
    various reports of problems on NetBSD & macOS hosts.  These were also
    tweaked to allow enabling the feature on a host_cpu of amd64 (was only
    allowed on x86_64 before)."

Thanks...

-- 
     -Chad


  reply	other threads:[~2022-10-06 18:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-06  1:29 Chad Dougherty
2022-10-06 17:24 ` Adam Dinwoodie
2022-10-06 18:20   ` Chad Dougherty [this message]
2022-10-06 20:01   ` Ken Brown
2022-10-09 14:23 ` Jon Turney
2022-10-09 21:18   ` Brian Inglis
2022-10-10  0:28   ` Chad Dougherty
2022-10-10  7:15     ` ASSI
2022-10-26  0:44   ` Chad Dougherty
2022-12-02 15:07   ` Jon Turney

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=0a7633f3-f5ed-b436-6b5f-d7adbf9d37ba@acm.org \
    --to=crd@acm.org \
    --cc=cygwin-apps@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).