autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Cross-platform availability of header files


From: Thomas Jahns
Subject: Re: Cross-platform availability of header files
Date: Fri, 15 Mar 2013 11:13:51 +0100
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.16) Gecko/20121215 Iceowl/1.0b1 Icedove/3.0.11

On 03/15/2013 02:19 AM, Zack Weinberg wrote:
> I've been doing research into the cross-platform availability of
> header files that are commonly probed for in Autoconf scripts.
> Results so far are here:
> http://www.owlfolio.org/possibly-useful/notes-on-the-cross-platform-availability-of-header-files/
>  Based on what I've learned, I have some questions for y'all:

although you didn't ask: aio.h does not need to be probed for: unistd.h defines
_POSIX_ASYNCHRONOUS_IO when it's available.

See <http://pubs.opengroup.org/onlinepubs/007904875/basedefs/unistd.h.html> for
some other features that don't require autoconf to check for, sys/mman.h is in
the same category.

With respect to your comment on identifiers with leading underscore: to be
conformant to e.g. C89 standards, an implementation must not define anything
without said leading underscore, but in cases where the non-standard
functionality is required to implement standard-mandated functionality, it's
easiest to have it available with a leading underscore.

In case you still need it, I could check AIX 6.1 for any header you want to know
about or provide an ls -R of /usr/include, although some of that are packaged
products and e.g. aio requires the installation of an optional kernel extension
package although I'm not sure if the header is available even when said package
is not installed.

Regards, Thomas
-- 
Thomas Jahns
DKRZ GmbH, Department: Application software

Deutsches Klimarechenzentrum
Bundesstra├če 45a
D-20146 Hamburg

Phone: +49-40-460094-151
Fax: +49-40-460094-270
Email: Thomas Jahns <address@hidden>

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]