This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug libc/11882] New: Should headers default to strict ISO C99?
- From: "carlos at codesourcery dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 4 Aug 2010 18:15:18 -0000
- Subject: [Bug libc/11882] New: Should headers default to strict ISO C99?
- Reply-to: sourceware-bugzilla at sourceware dot org
The following commit:
http://sourceware.org/git/?p=glibc.git;a=commit;h=3e6b0a28ebc2319262b318790019558f78249c8b
updates the include/features.h headers to default _POSIX_C_SOURCE to 200809L,
this in turn defines __USE_ISOC99 to 1, and this causes the headers to trigger
strict ISO C99 mode which redirects sscanf to __isoc99_sscanf.
Applications that were previously using the sscanf format specifier '%a' (a GNU
extension) stop working. Using -std=gnu89, -std=gnu99 does not allow you to get
back the previous behaviour. Using -std=c89 or -D_GNU_SOURCE restores the
previous behaviour of supporting '%a' (now '%m' in POSIX).
The compiler is still defaulting to -std=gnu89.
Is it glibc's intent to default to strict ISO C99 mode?
--
Summary: Should headers default to strict ISO C99?
Product: glibc
Version: 2.12
Status: NEW
Severity: normal
Priority: P2
Component: libc
AssignedTo: drepper at redhat dot com
ReportedBy: carlos at codesourcery dot com
CC: glibc-bugs at sources dot redhat dot com
GCC build triplet: arm-none-linux-gnueabi
GCC host triplet: arm-none-linux-gnueabi
GCC target triplet: arm-none-linux-gnueabi
http://sourceware.org/bugzilla/show_bug.cgi?id=11882
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.