From: Warren Young <wyml@etr-usa.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Problem with new acl code and cdrtools
Date: Tue, 09 Feb 2016 08:46:00 -0000 [thread overview]
Message-ID: <BAF8618B-B333-4391-91B9-17174761484C@etr-usa.com> (raw)
In-Reply-To: <CAFo71_58PFDgaNU4-bdj4JoCndXAd=+i57w_eAgeq==RVcyoDw@mail.gmail.com>
On Feb 9, 2016, at 12:56 AM, Ismail Donmez <ismail@i10z.com> wrote:
>
> On Tue, Feb 9, 2016 at 6:14 AM, Warren Young <wyml@etr-usa.com> wrote:
>> On Feb 8, 2016, at 9:59 AM, Ismail Donmez <ismail@i10z.com> wrote:
>>>
>>> Thats a hack :)
>>
>> Peter’s proposal is as far from a hack as it gets.
>
> What Peter suggests is telling autoconf to assume aclfromtext() does
> not exist on the system which is a hack and I already have a hack I
> could use.
No. Once again, he’s suggesting that you write a *test* that checks whether aclfromtext() exists here. Hypothesis -> test -> decision is science, not assumption or hackery.
>> #include <config.h>
>> #if HAVE_FUNC_ACLFROMTEXT
>> # include <cygwin/acl.h>
>> #endif
>
> I could check for __cygwin__ instead of that which would do the same thing.
Not if it’s Cygwin 1.7.34.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-02-09 8:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-08 10:02 Ismail Donmez
2016-02-08 13:18 ` Corinna Vinschen
2016-02-08 13:31 ` Ismail Donmez
2016-02-08 14:10 ` Corinna Vinschen
2016-02-08 14:14 ` Ismail Donmez
2016-02-08 14:36 ` Corinna Vinschen
2016-02-08 16:10 ` Ismail Donmez
2016-02-08 19:24 ` Yaakov Selkowitz
2016-02-09 9:36 ` Corinna Vinschen
2016-02-08 16:29 ` Peter Rosin
2016-02-08 17:00 ` Ismail Donmez
2016-02-09 4:14 ` Warren Young
2016-02-09 7:57 ` Ismail Donmez
2016-02-09 8:46 ` Warren Young [this message]
2016-02-09 8:50 ` Ismail Donmez
2016-02-09 8:57 ` Peter Rosin
2016-02-09 9:06 ` Ismail Donmez
2016-02-09 10:13 ` Peter Rosin
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=BAF8618B-B333-4391-91B9-17174761484C@etr-usa.com \
--to=wyml@etr-usa.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).