Ralf Wildenhues wrote:
I haven't followed this thread, so bear with me, please.
No worries :-). It looks like you noticed everything that is gnulib-related.
* Matthew Woehlke wrote on Wed, Apr 29, 2009 at 06:09:51PM CEST:
For now I'm just going to use 'CC="cc -qlanglvl=stdc99"'. I don't know
how hard you want to try to make this work out of the box, but the
previous change should probably be reverted.
Typically, -qlanglvl=extc99 is a better choice for GNU software.
I tried that also, but it results in configure picking '-qlanglvl=extc99
-qlanglvl=ansi', which presumably defeats the purpose. (IOW, extc99 mode
is not C89-compliant as autoconf is checking for that; stdc99 mode
however is accepted.)
FYI: adding the autoconf check to turn on c99 mode is broken; autoconf
picks up -qlanglvl=ansi from the ANSI c89 check, and doesn't know how to
try alternatives (this affects other GNU packages as well, most notably
coreutils).
Can you reformulate this paragraph so that it can serve as a bug report
against Autoconf and/or other affected GNU packages? IOW: what exactly
is broken, using AC_PROG_CC_C99 after AC_PROG_CC_C89?
I've no idea. I just know that at least coreutils does it in such a way
that configure doesn't figure out to use either of
-qlanglvl={std,ext}c99. And that I've seen the same thing in other packages.
--
Matthew
Please do not quote my e-mail address unobfuscated in message bodies.
--
This is not a sig. I am too lazy to steal one, perhaps you could loan me
yours? -- Unknown
