On Fri, 25 Jul 2014, Jan-Benedict Glaw wrote: > On Thu, 2014-07-24 16:30:13 -0400, Hans-Peter Nilsson <h...@bitrange.com> > wrote: > > On Thu, 24 Jul 2014, Jan-Benedict Glaw wrote: > > > On Tue, 2014-07-22 16:40:31 -0400, Hans-Peter Nilsson <h...@bitrange.com> > > > wrote: > > > > 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...)
I think we have different definitions of "getting most targets to build". I guess a valid reply here would IMO have been an empty list. :( Does 4.9.1 work(*)? > > On gcc110 which *has* gnat, I get: > > /gcc/o/aarch64-elf/./mpfr -I/home/hp/gcc/gcc/mpfr -I/opt/cfarm/mpc/include > > -I../../../gcc/gcc/../libdecnumber -I../../../gcc/gcc/../libdecnumber/dpd > > -I../libdecnumber -I../../../gcc/gcc/../libbacktrace -o dwarf2out.o -MT > > dwarf2out.o -MMD -MP -MF ./.deps/dwarf2out.TPo ../../../gcc/gcc/dwarf2out.c > [...] > > The config-list.mk builds are right now only scheduled on gcc20 and > gcc76. Maybe I'd schedule them on gcc110 as well? I wouldn't bother, as I found most fail with the errored-warning I quoted, the rest on port warnings (c6x, mep, avr, bfin, so far) I'm guessing you don't get very far on gcc20 or gcc76 on each target. I think there's a miscommunication here. When you said you used config-list.mk and by reporting target-specific build errors, I misunderstood that as implying that most targets were then building with no errors using config-list.mk. > > Perhaps you have local patches or did you call config-list.mk > > with some kind of options? Maybe you didn't actually use > > config-list.mk? Or just looked to see whether the first failure > > for each target was on a target-specific file or the (same) > > middle-end bits? Ok, I'm out of guesses. :) > > ...and you just missed the most obvious one: It probably won't just > work at all ;-) (Not really, that's reporting the first failure for a target when being a target-specific error.) Anyway, on to the point of this message: by the quoted list it seems you have a local host called pluto using 4.9.1 as the host gcc for some build; does config-list.mk work for that? (* to wit, by "work" I mean "builds with no errors for at least one target actually using config-list.mk".) brgds, H-P
