This is the mail archive of the java-patches@gcc.gnu.org mailing list for the Java project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
Hi, On Fri, 2004-03-26 at 11:28, Michael Koch wrote: > Am Freitag, 26. März 2004 11:09 schrieb Mark Wielaard: > > I don't believe it is really designed for a particular C-dialect. But > > it would be nice if it is compilable with gcc-2.95. It seems gcc-2.95 > > supports -std=c9x so we can switch to that. But I cannot figure out > > how to convince Autoconf that I want that dialect used for my C > > files. Clues anybody? > > Added AM_CFLAGS=-std=c89 in the Makefile.am is one option but it would > mean we need to add it to all Makefile.am in all dirs with native code. > > CFLAGS=$CFLAGS -std=c89 > AC_SUBST(CFLAGS) > > This in configure.ac is another option. > > The only problem I see is that we probably support non-gcc compilers > that dont support this flag. What will they do when they see it ? Precisely. We seem to already just override CFLAGS in configure.ac for the braindead Red Hat gcc-2.96 compiler that generates wrong code for -O2... So maybe we should just give up on other compilers then the gcc variants out there. But I had hoped Autoconf would make it easy to specify the wanted C dialect. Cheers, Mark
Attachment:
signature.asc
Description: This is a digitally signed message part
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |