From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27522 invoked by alias); 22 May 2018 01:08:15 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 27512 invoked by uid 89); 22 May 2018 01:08:14 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,SPF_PASS,URIBL_RED autolearn=ham version=3.3.2 spammy=Hx-languages-length:1327 X-HELO: mailbackend.panix.com X-Gm-Message-State: ALKqPwc1zrv8medssJYvQCWmuBhQXudxirfnafa7nFi2BR/xL99o9vLY Pm3jrMt+Xaxn70wIGUZnBa8bbYwTbTwMhYq1Cug= X-Google-Smtp-Source: AB8JxZpdO+jl0SFg2G7IqDP4R0Ue6SAb6j5uAqH5twIXZTidW1b/Dh73ucAk/IlKW8gLcVuwJOd9bGPkip8HEn9i+qM= X-Received: by 2002:a9d:2c65:: with SMTP id f92-v6mr14364649otb.74.1526951290478; Mon, 21 May 2018 18:08:10 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <20180521173853.5172-1-zackw@panix.com> <20180521173853.5172-5-zackw@panix.com> From: Zack Weinberg Date: Tue, 22 May 2018 01:08:00 -0000 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH 4/4] New configure option --disable-crypt. To: Joseph Myers Cc: GNU C Library , "Carlos O'Donell" , Florian Weimer , Rical Jasan , Thorsten Kukuk Content-Type: text/plain; charset="UTF-8" X-SW-Source: 2018-05/txt/msg00704.txt.bz2 On Mon, May 21, 2018 at 6:34 PM, Joseph Myers wrote: > On Mon, 21 May 2018, Zack Weinberg wrote: > >> On Mon, May 21, 2018 at 3:51 PM, Joseph Myers wrote: >> > On Mon, 21 May 2018, Zack Weinberg wrote: >> > >> >> unistd.h continues to define _XOPEN_CRYPT to 1 and to declare crypt. >> > >> > I'd expect _XOPEN_CRYPT to change in patch 1, since it includes encrypt >> > and setkey. >> >> 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. Making _XOPEN_CRYPT be -1 or undefined in current conformance modes would be a disservice to any program that is actually using it, since it is overwhelmingly likely that they are using it to detect crypt, not encrypt or setkey. > The conform/ data is in any case meant to correspond to the standard > versions in question (plus defect corrections from TCs etc., not plus > feature changes from other revisions to the standard). Intentionally > unsupported features are listed in that data with appropriate XFAILs (see > e.g. those for varargs.h in conform/Makefile). This I can change. zw