public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Peter Rosin <peda@lysator.liu.se>
To: cygwin@cygwin.com
Subject: Re: Problem with new acl code and cdrtools
Date: Tue, 09 Feb 2016 08:57:00 -0000	[thread overview]
Message-ID: <56B9A9D8.1030900@lysator.liu.se> (raw)
In-Reply-To: <CAFo71_58PFDgaNU4-bdj4JoCndXAd=+i57w_eAgeq==RVcyoDw@mail.gmail.com>

On 2016-02-09 08:56, Ismail Donmez wrote:
> Hi,
> 
> 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:
>>>
>>> On Mon, Feb 8, 2016 at 6:29 PM, Peter Rosin <peda@lysator.liu.se> wrote:
>>>> On 2016-02-08 14:31, Ismail Donmez wrote:
>>>>> This is a generic code so I don't want to add a cygwin specific
>>>>> dependency there. Is there a preprocessor definition for cygwin
>>>>> version? I could use that to disable HAVE_SUN_ACL for cygwin 2.5+
>>>>
>>>> Pardon me for butting in, but isn't adding a Cygwin version check
>>>> about as non-generic as it gets?
>>>>
>>>> Wouldn't something like this work:
>>>>
>>>> .../configure ac_cv_func_aclfromtext=no
>>>
>>> Thats a hack :)
>>
>> I don’t know if that smiley means you’re joking or if you’re just trying to soften a negative judgement, but 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.
> 
>> He is proposing that you write an autoconf test that determines if the platform has this new ACL behavior.  Then in your C code:
>>
>>    #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.
> 
> Anyhow the discussion diverged a lot, and for now I'll be using my
> simple hack of disabling HAVE_SUN_ACL manually.

My take on the situation was that you could disable SUN ACLs by telling
configure that cdrtools should not use aclfromtext(), and that the code
that backs this was already in place. I.e. that you could get a working
build recipe w/o any hacking/patching of cdrtools at all.

I might be misunderstanding something though, but if it works and if
it is considered more of an hack than introducing a cygwin version
check inside the cdrtools package, then that's not my headache.

Just trying to help...

Cheers,
Peter

--
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

  parent reply	other threads:[~2016-02-09  8:57 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
2016-02-09  8:50               ` Ismail Donmez
2016-02-09  8:57             ` Peter Rosin [this message]
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=56B9A9D8.1030900@lysator.liu.se \
    --to=peda@lysator.liu.se \
    --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).