This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH 4/4] New configure option --disable-crypt.
- From: Zack Weinberg <zackw at panix dot com>
- To: Florian Weimer <fweimer at redhat dot com>
- Cc: Joseph Myers <joseph at codesourcery dot com>, GNU C Library <libc-alpha at sourceware dot org>, "Carlos O'Donell" <carlos at redhat dot com>, Rical Jasan <rj at 2c3t dot io>, Thorsten Kukuk <kukuk at suse dot de>
- Date: Wed, 20 Jun 2018 18:47:58 -0400
- Subject: Re: [PATCH 4/4] New configure option --disable-crypt.
- References: <20180521173853.5172-1-zackw@panix.com> <20180521173853.5172-5-zackw@panix.com> <alpine.DEB.2.20.1805211950530.30181@digraph.polyomino.org.uk> <CAKCAbMi5-c+nrt3apH-rnvi1jX+4ShLJ140ZvzjqEGrcoETs9w@mail.gmail.com> <alpine.DEB.2.20.1805212226550.30181@digraph.polyomino.org.uk> <fa94a6a5-02af-4d60-fe8f-cd827ec8c1d3@redhat.com>
On Wed, Jun 20, 2018 at 4:40 PM, Florian Weimer <fweimer@redhat.com> wrote:
> On 05/22/2018 12:34 AM, Joseph Myers wrote:
>> On Mon, 21 May 2018, Zack Weinberg wrote:
>>> No, this is an intentional deviation from the present state of POSIX,
>>> anticipating the removal of those functions from the standard.
>>
>> That would only seem relevant to the _XOPEN_CRYPT value in future POSIX
>> modes, not current ones.
>
> So we should stop defining _XOPEN_CRYPT, but continue to declare crypt in
> <unistd.h> for __USE_MISC || __USE_XOPEN? That would work for me.
Again, I think that it is inappropriate to stop defining _XOPEN_CRYPT
in any mode. Yes, this is an intentional deviation from POSIX, but I
think it is far less likely to break existing programs than the
alternative.
zw