From: Ismail Donmez <ismail@i10z.com>
To: cygwin@cygwin.com
Subject: Re: Problem with new acl code and cdrtools
Date: Tue, 09 Feb 2016 09:06:00 -0000 [thread overview]
Message-ID: <CAFo71_7Q4C73ec_ULtBESxg5Q1P-QmLxHCQYqjfssQKDt4HxZA@mail.gmail.com> (raw)
In-Reply-To: <56B9A9D8.1030900@lysator.liu.se>
Hi Peter,
On Tue, Feb 9, 2016 at 10:56 AM, Peter Rosin <peda@lysator.liu.se> wrote:
> 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...
If my reply came out as rude, I am sincerely sorry. As you said yes
this would be a way to fix the situation for Cygwin, but I would be
more happy with a pre-processor macro which we can use for this.
Anyhow.
Thanks,
ismail
--
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 9:06 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
2016-02-09 9:06 ` Ismail Donmez [this message]
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=CAFo71_7Q4C73ec_ULtBESxg5Q1P-QmLxHCQYqjfssQKDt4HxZA@mail.gmail.com \
--to=ismail@i10z.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).