Date: Mon, 29 Sep 1997 14:51:27 -0600 From: Warner Losh <imp@village.org> To: Bruce Evans <bde@zeta.org.au>, cvs-all@freebsd.org, cvs-committers@freebsd.org, cvs-usrbin@freebsd.org Subject: Re: cvs commit: src/usr.bin/make main.c var.c Message-ID: <199709292051.OAA13443@harmony.village.org> In-Reply-To: Your message of "Mon, 29 Sep 1997 14:12:49 MDT." <199709292012.OAA13253@harmony.village.org> References: <199709292012.OAA13253@harmony.village.org> <199709291242.WAA01186@godzilla.zeta.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199709292012.OAA13253@harmony.village.org> Warner Losh writes: : I'll have to look into this more closely. I think that DUX's cc : defines __STDC__ to be 0 unless you are exactly ansi. Stupid, imho, : but I think that's what's up. I'll have to check into the details of : this more closely when I have better connectivity to the alpha. What is going on here is that DUX defines __STDC__ to be 0 when -std is on the command line, to 1 when -std1 is on the command line, and to nothing at all when -std0 is on the command line. These conditions correspond to default compile, -ansi and -traditional for gcc (approx). The default is -std0, so that's why I was seeing what I was seeing. Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709292051.OAA13443>