glibc compliance to POSIX and SUS

From: marcelpaulo (yagpaulo-login_at_yahoo.com)
Date: 10/31/05 

Date: 31 Oct 2005 06:04:31 -0800

Hi,

If I define feature test macro _POSIX_SOURCE, glibc will comply to
which edition of the POSIX.1 standard ?

And _XOPEN_SOURCE to which SUS version ?

I'm running:
GNU/Linux Debian sid distribution
Kernel 2.6.14-1-686
libc6 2.3.5-7

Read all docs that come with libc6 and glibc-doc but couldn't get a
clear answer.

Thanks
Paulo

Relevant Pages

  • Re: Detecting overflows while computing off_t
    ... OFF_MAX and since off_t is a signed integer type, ... Cray vector machines have padding bits for some integer types; ... hacks to be able to use standard features on a conforming ... implementation (standard = SUS, not ISO 9899). ...
    (comp.lang.c)
  • forestalling GNU incompatibility - proposal for binary relative dynamic linking
    ... After spending *two weeks* on various ways of building glibc, ... glibc with fifty patches. ... to a 'standard' out of the box glibc build. ... then the SuSE executables work fine but my new executables break, ...
    (Linux-Kernel)
  • Portability / Conditional Compilation
    ... standards, POSIX, Win32, SUS, BSD, and occasionally a glibc extension. ... programmer reason about conditionally compiling for a feature when they ... When do you code to standards or architecture or compiler? ... for UNIX98 as the standard base. ...
    (comp.unix.programmer)
  • Re: bash vs ksh?
    ... SUS, and SUS (not Posix) defines Unix ... volumes of) SUS were merged to form a single standard ...
    (comp.unix.shell)
  • Re: strtod - Dynamic Memory?
    ... the library (glibc) is behaving as documented for the library. ... > A floating point number in decimal or hexadecimal format. ... that it uses the term "decimal-point character" rather than "period" ... The actual C99 standard has identical wording; ...
    (comp.lang.c)