This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: need to define _ISOC99_SOURCE
- To: Akim Demaille <akim at epita dot fr>
- Subject: Re: need to define _ISOC99_SOURCE
- From: Bruno Haible <haible at ilog dot fr>
- Date: Tue, 1 Aug 2000 20:19:54 +0200 (CEST)
- Cc: Paul Eggert <eggert at twinsun dot com>, jsm28 at cam dot ac dot uk, libc-alpha at sourceware dot cygnus dot com, autoconf at gnu dot org
- References: <Pine.SOL.4.21.0007261506580.6571-100000@red.csi.cam.ac.uk><m3lmyoamkf.fsf@otr.mynet.cygnus.com><200007262030.NAA15438@ruby.twinsun.com><14719.22225.713527.823418@honolulu.ilog.fr><mv4vgxrx6ki.fsf@nostromo.lrde.epita.fr><200007271634.JAA08859@green-office.twinsun.com><mv4n1iymwrq.fsf@nostromo.lrde.epita.fr><14725.40424.405013.773855@honolulu.ilog.fr><mv466pme1pc.fsf@nostromo.lrde.epita.fr><200007312139.OAA01047@ruby.twinsun.com><mv43dkpnk3p.fsf@nostromo.lrde.epita.fr><14726.57585.66730.177665@honolulu.ilog.fr><mv4punsnag8.fsf@nostromo.lrde.epita.fr>
Akim Demaille writes:
> Bruno> Well, as Paul Eggert said, it is preferrable to try to append
> Bruno> "-Ae" to $CC (and $CPP) instead of defining _HPUX_SOURCE. "cc
> Bruno> -Ae" gives you "long long" support, which _HPUX_SOURCE doesn't.
>
> Yep, maybe, but I fear it is somewhat different: does it mean you're
> requiring ANSI C? If it does not, then fine with me.
"cc -Ae" (equivalent to "cc -Aa -D_HPUX_SOURCE +e", where "+e" enables
"HP value-added features", i.e. some C language features which are not
strictly ANSI C) groks both ANSI C and K&R C syntaxes. Whereas plain
"cc -D_HPUX_SOURCE" does not grok ANSI C source, only K&R source.
Bruno