Re: werror fallout for cross-builds (was: Re: [BUILDROBOT][PATCH] Fix mmix (unused variable))

[Jan-Benedict Glaw <jbglaw@lug-owl.de>]

[-- Attachment #1: Type: text/plain, Size: 1714 bytes --]

On Tue, 2014-07-22 16:40:31 -0400, Hans-Peter Nilsson <hp@bitrange.com> wrote:
> In the name of "dealing with the fallout": with the patch below
> (don't forget to re-generate configure) I get build errors in
> generic code r212915 for *both* x86_64 "gcc version 4.7.2
> 20120921 (Red Hat 4.7.2-2) (GCC)" for mmix-knuth-mmixware:
[...]
> I guess both of these can be attributed to "fairly old or even
> broken" host gcc if you want to stretch it...
> 
> Jan-Benedict, which host gcc version do you use when getting
> most targets to build with config-list.mk?  Maybe we can just
> set the initial version to that instead of 4.4.4.

darkeye		gcc (Debian 4.8.1-7) 4.8.1
gccbuild	gcc (Debian 4.8.1-7) 4.8.1
pluto		gcc (Debian 4.9.1-1) 4.9.1
gcc20		gcc (Debian 4.4.5-8) 4.4.5
gcc76		gcc (Debian 4.4.5-8) 4.4.5
gcc110		gcc (GCC) 4.7.2 20121109 (Red Hat 4.7.2-8)
gcc111		gcc (GCC) 4.8.1
		XL 12.1.0.0 (if I ever get that properly working...)

> For reference, the patch, which works as intended (-Werror in
> the gcc build directory for cross-builds by default, not
> affecting native builds and not at all for gcc < 4.4.4).  (Vax
> is excepted, see J-B's previous post.)  I'd ask for approval

VAX sould work, it's pdp11 that I said wouldn't.

> except now the fallout seems excessive as both my common setups
> fail building, while having reasonable testsuite results, and I
> don't know my way around the erroring part of the code:

MfG, JBG

-- 
      Jan-Benedict Glaw      jbglaw@lug-owl.de              +49-172-7608481
Signature of:              Fortschritt bedeutet, einen Schritt so zu machen,
the second  :                   daß man den nächsten auch noch machen kann.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]