On 20 December 2017 at 09:31, Paulo Matos <pmatos@linki.tools> wrote: > > > On 15/12/17 10:21, Christophe Lyon wrote: >> On 15 December 2017 at 10:19, Paulo Matos <pmatos@linki.tools> wrote: >>> >>> >>> On 14/12/17 21:32, Christophe Lyon wrote: >>>> Great, I thought the CF machines were reserved for developpers. >>>> Good news you could add builders on them. >>>> >>> >>> Oh. I have seen similar things happening on CF machines so I thought it >>> was not a problem. I have never specifically asked for permission. >>> >>>>> pmatos@gcc115:~/gcc-8-20171203_BUILD$ as -march=armv8.1-a >>>>> Assembler messages: >>>>> Error: unknown architecture `armv8.1-a' >>>>> >>>>> Error: unrecognized option -march=armv8.1-a >>>>> >>>>> However, if I run the a compiler build manually with just: >>>>> >>>>> $ configure --disable-multilib >>>>> $ nice -n 19 make -j4 all >>>>> >>>>> This compiles just fine. So I am at the moment attempting to investigate >>>>> what might cause the difference between what buildbot does and what I do >>>>> through ssh. >>>>> >>>> I suspect you are hitting a bug introduced recently, and fixed by: >>>> https://gcc.gnu.org/ml/gcc-patches/2017-12/msg00434.html >>>> >>> >>> Wow, that's really useful. Thanks for letting me know. >>> >> And the patch was committed last night (r255659), so maybe your builds now >> work? >> > > On some machines, in incremental builds I still seeing this: > Assembler messages: > Error: unknown architectural extension `lse' > Error: unrecognized option -march=armv8-a+lse > make[4]: *** [load_1_1_.lo] Error 1 > make[4]: *** Waiting for unfinished jobs.... > > Looks related... the only strange thing happening is that this doesn't > happen in full builds. >
The recent fix changed the Makefile and configure script in libatomic. I guess that if your incremental builds does not run configure, it's still using old Makefiles, and old options. > -- > Paulo Matos
