httpd-apreq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Max Kellermann <...@duempel.org>
Subject Re: [PATCH] second snapshot of my "let's kill void*env" patch
Date Thu, 20 Jan 2005 19:59:34 GMT
On 2005/01/13 05:26, Joe Schaefer <joe+gmane@sunstarsys.com> wrote:
> We still support ancient ansi C compilers and non-gcc platforms, so
> IMO using the -std=c99 flag isn't appropriate for us yet.

I am trying to compile apreq with -ansi - but that does not work, as
the libapr headers are not ANSI C compliant. Neither is Apache, the
AP_INIT_TAKE1 macro generates ANSI C warnings we can't disable by
using -isystem:

mod_apreq.c:780: warning: ISO C90 forbids specifying subobject to
initialize
mod_apreq.c:782: warning: ISO C90 forbids specifying subobject to
initialize
mod_apreq.c:784: warning: ISO C90 forbids specifying subobject to
initialize
mod_apreq.c:786: warning: ISO C90 forbids specifying subobject to
initialize

apr-config --cppflags says:

 -DLINUX=2 -D_REENTRANT -D_XOPEN_SOURCE=500 -D_BSD_SOURCE
  -D_SVID_SOURCE -D_GNU_SOURCE

why -D_GNU_SOURCE? that adds several GNU extensions.

Now which C standard is supported by Apache? Their documentation says
ANSI, but that is apparently wrong. If they do not support ANSI C, it
gives no advantage if we do.

Max


Mime
View raw message