I've just noticed that a slower cross compiler build can be killer by a builder service: [ 24s] + ../configure --prefix=/usr --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64 --enable-languages=c,c++ --enable-checking=release --disable-werror --with-gxx-include-dir=/usr/include/c++/13 --with-libstdcxx-zoneinfo=/usr/share/zoneinfo --enable-ssp --disable-libssp --disable-libvtv --enable-cet=auto --disable-libcc1 --disable-plugin --with-bugurl=https://bugs.opensuse.org/ '--with-pkgversion=SUSE Linux' --with-slibdir=/usr/arm-suse-linux-gnueabi/sys-root/lib64 --with-system-zlib --enable-libstdcxx-allocator=new --disable-libstdcxx-pch --enable-version-specific-runtime-libs --with-gcc-major-version-only --enable-linux-futex --enable-gnu-indirect-function --program-suffix=-13 --program-prefix=arm-none-eabi- --target=arm-none-eabi --disable-nls --with-sysroot=/usr/arm-suse-linux-gnueabi/sys-root --with-build-sysroot=/usr/arm-suse-linux-gnueabi/sys-root --with-build-time-tools=/usr/arm-suse-linux-gnueabi/bin --with-newlib --enable-multilib --with-multilib-list=aprofile,rmprofile --disable-decimal-float --disable-libffi --disable-libgomp --disable-libmudflap --disable-libquadmath --disable-shared --disable-threads --disable-tls --disable-bootstrap --enable-link-mutex --disable-libsanitizer --build=x86_64-suse-linux --host=x86_64-suse-linux ... [ 1113s] esac; \ [ 1113s] done [ 1113s] make[3]: Leaving directory '/home/abuild/rpmbuild/BUILD/gcc-13.0.1+git6506/obj-x86_64-suse-linux/arm-none-eabi/libgcc' [ 1762s] make[1]: Entering directory '/home/abuild/rpmbuild/BUILD/gcc-13.0.1+git6506/obj-x86_64-suse-linux' [ 1762s] Checking multilib configuration for libstdc++-v3... [ 1762s] mkdir -p -- arm-none-eabi/libstdc++-v3 [ 1762s] Configuring in arm-none-eabi/libstdc++-v3 As seen, at this place there's no output and the step takes 600s on a pretty fast machine. So please, emit an output so that it doesn't get killer by a builder.
Build example where it's killed: https://build.opensuse.org/package/live_build_log/devel:gcc:next/gcc13:cross-arm-none-gcc13/openSUSE_Factory_ARM/aarch64 [13016s] make[3]: Leaving directory '/home/abuild/rpmbuild/BUILD/gcc-13.0.1+git6506/obj-aarch64-suse-linux/arm-none-eabi/libgcc' [18421s] qemu-system-aarch64: terminating on signal 15 from pid 48801 (<unknown process>) Job seems to be stuck here, killed. (after 5400 seconds of inactivity) [18425s] ### VM INTERACTION END ###
Are you sure it's not really stuck? Is it linking many target libs in parallel?
(In reply to Richard Biener from comment #2) > Are you sure it's not really stuck? Is it linking many target libs in > parallel? Dunno, it's slow even on a reasonably fast machine, so I can imagine it can take hours on a slow builder. It's not linking, it's running configure serially.
This appears to be the effect of make's output sync, and configuring umpteen multilibs just takes a long time (3357s during the last sucessful build).
aprofile is 10 multilibs and rmprofile is 21 multilibs. so 31 multilibs in total (if I counted correctly). that is a lot of building in general.
(In reply to Andreas Schwab from comment #4) > This appears to be the effect of make's output sync, and configuring umpteen > multilibs just takes a long time (3357s during the last sucessful build). Yes, I think this is just make -Oline or similar. I see the same sort of thing when I use it. There might be a real problem it was masking but without the logs it's hard to say.