Hi Christophe, On Tue, Aug 16, 2022 at 01:54:00PM +0200, Christophe Lyon wrote: > On 8/12/22 18:44, Mark Wielaard wrote: > > The ubuntu22_04-arm64 worker seems to happily do full gcc bootstrap > > and check builds: > > https://builder.sourceware.org/buildbot/#/workers/34 > > > > It does find a couple of failing testcases, which you might want to > > look at, but most seem expected. All results are recorded in bunsen to > > be compared. > > Great, thanks! I guess the errors are the same as observed on > gcc-full-debian-arm64? I assume so, but don't have internet access at the moment to check. You can use the bunsen results database to compare different builds: https://builder.sourceware.org/testruns/ > Anyway I don't think any target has a clean 'make check' in GCC :-( > > This will increase the need for a regression-detection mechanism in the > buildbot, otherwise we'll only have red bullets which people will ignore.... Yes. I am hoping we can use the bunsen results database to check for regressions. We have the current build number of the builder, so we should be able to pull the bunsen results of the previous build. Then we should be able to compare the dejagnu summary. > > The ubuntu22_04-armhf worker however fails to do a full gcc build: > > https://builder.sourceware.org/buildbot/#/workers/33 > > > > In file included from ../../../gcc/libgcc/../gcc/tsystem.h:87, > > from ../../../gcc/libgcc/libgcc2.c:27: > > /usr/include/stdio.h:27:10: fatal error: bits/libc-header-start.h: No such file or directory > > 27 | #include > > | ^~~~~~~~~~~~~~~~~~~~~~~~~~ > > compilation terminated. > > > > It looks like that happens while building libcc for > > armv8l-unknown-linux-gnueabihf. Maybe missing devel header files? Or > > does the build needs to be configured to exclude this target? > > So... I dug a bit and... you need to add --with-float=hard on GCC's > configure line. For some reason GCC's configure is not able to infer > that from the trailing 'hf' in the target name. Can you add it for this > target only or is the configure line shared by all GCC workers? Currently the configure line is shared by all gcc-full builders. But that can be changed. As in the attached patch (apologies for my python skills). I'll push it once I have internet access again. Cheers, Mark