[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Problem in Tru64 with autoconf choosen cc flags [PATCH]
From: |
Paul Eggert |
Subject: |
Re: Problem in Tru64 with autoconf choosen cc flags [PATCH] |
Date: |
14 Jan 2004 10:30:52 -0800 |
User-agent: |
Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 |
Nicolás Lichtmaier <address@hidden> writes:
> In Tru64 autoconf likes to select "-std1" as the flag to get an ANSI
> compiler.
I think that change was proposed by Kevin Ryde in June
<http://mail.gnu.org/archive/html/autoconf-patches/2003-06/msg00009.html>
and was later installed into Autoconf. The problem is that plain "cc"
mishandles \x escapes in strings.
> The problem is that this is similar to the "-ansi" switch in
> GCC, and it turns off useful extensions.
What extensions are these? Is this documented anywhere?
> The normal and recommended switch would be just "-std".
Besides \x,
<http://groups.google.com/groups?selm=9ro8ef%2427l6%241%40FreeBSD.csie.NCTU.edu.tw>
says that Tru64 "cc -std" defines __STDC__ to be 0. It's clearly more
conservative to use -std1, but perhaps if -std1 disables some useful
extensions then we should revisit this issue.
Re: Problem in Tru64 with autoconf choosen cc flags [PATCH], Kevin Ryde, 2004/01/14