Re: PATCH for java warnings (ANSI string concat)

[Per Bothner <per at bothner dot com>]

I guess we never came to a conclusion last time we discussed whether
the backends should be written in K&R C.  I see no reason they should
(except perhaps stylistic consistency).  Personally, I don't
understand why we want the non-c language front-ends to compile with
-Wtraditional.

Instead we really should fix the gcc compilation framework so it is consistent
with other GNU programs.  Specifically (assuming a native build).

all:
        make all.indirect LANGUAGES=C
        make stage1
        make all.indirect CC="stage1/xgcc -Bstage1/" CFLAGS="-g -O2" LANGUAGES="$(LANGUAGES)"

(This is simplified and probably wrong.)

Building a cross-compiler is hairier; we don't necessarily need to make
it conform to my guideline.  Thgough you might still do something like:

all:
        make native-compiler LANGUAGES=C
        make stage1
        re-configure
        make all.indirect CC="stage1/xgcc -Bstage1/" CFLAGS="-g -O2" LANGUAGES="$(LANGUAGES)"
-- 
	--Per Bothner
per@bothner.com   http://www.bothner.com/~per/