From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: cygwin/acl.h not included from sys/acl.h
Date: Thu, 18 Oct 2018 09:06:00 -0000 [thread overview]
Message-ID: <20181018090642.GZ7872@calimero.vinschen.de> (raw)
In-Reply-To: <1165926610.11966611.1539851450039@mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
On Oct 18 08:30, matthew patton via cygwin wrote:
> Many of the headers in 'sys' include their counterparts from 'cygwin'.
> Why is acl.h special? I see the comment on line 25 but I'm missing the
> point, I guess - not seeing the collisions.
Not collisions, namespace poisoning. cygwin/acl.h defines the
old Solaris macros and function calls, but a POSIX application
should be free to use functions like "acl" by itself.
> 'cygwin/acl.h' is a very important file.
No, it isn't, if you're using POSIX ACLs.
> Granted I don't normally
> compile much from source under Cygwin but I was building my own (very
> slightly) modified RSYNC and stumbled across the missing dependency.
>
> What is the correct solution if the 1-liner fix to sys/acl.h is not
> acceptable?
Build rsync with POSIX ACL support. It's already in the sources. It's
very likely that a simple autoconf (or autoreconf if you build from repo
sources) will do.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-10-18 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1165926610.11966611.1539851450039.ref@mail.yahoo.com>
2018-10-18 8:31 ` matthew patton via cygwin
2018-10-18 9:06 ` Corinna Vinschen [this message]
[not found] <1582687447.11951125.1539856293918.ref@mail.yahoo.com>
2018-10-18 9:51 ` matthew patton via cygwin
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=20181018090642.GZ7872@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).