[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Ensuring posix-ness
From: |
Bruno Haible |
Subject: |
Re: Ensuring posix-ness |
Date: |
Thu, 8 Sep 2011 12:04:33 +0200 |
User-agent: |
KMail/1.13.6 (Linux/2.6.37.6-0.5-desktop; KDE/4.6.0; x86_64; ; ) |
Eric Blake wrote:
> > But it is marked as [XSI]. I don't know whether that implies that glibc is
> > right in hiding the declaration, or it should enable it?
>
> Glibc bug. XSI shading means that a non-XSI implementation need not
> have crypt by default, but glibc is an XSI implementation, so requesting
> compliance with POSIX 2008 means that crypt() should be visible in
> <unistd.h>. There's no feature macro needed to turn on XSI functions -
> either you have an XSI system and they are all available by default, or
> you do not have an XSI system (usually embedded systems) and the system
> documents that it is not provide XSI.
Thanks for explaining.
> Would you care to raise a bug report against glibc?
Likewise about encrypt() in <unistd.h> and setkey() in <stdlib.h>.
Bruno
--
In memoriam Elisabeth von Thadden
<http://en.wikipedia.org/wiki/Elisabeth_von_Thadden>