I do have a tinderbox image where it failed here: * Touching libbacktrace/Makefile.in * Touching libbacktrace/configure * Touching libbacktrace/config.h.in >>> Source prepared. >>> Configuring source in /var/tmp/portage/dev-lang/gnat-gpl-2021-r5/work/gcc-10-2021-20210519-19A74-src ... /var/tmp/portage/dev-lang/gnat-gpl-2021-r5/temp/environment: line 1876: l1_cache_sizes[${l1_cache_size}]: bad array subscript * The ebuild phase 'configure' has exited unexpectedly. This type of * behavior is known to be triggered by things such as failed variable $ emerge -qpvO dev-lang/gnat-gpl [ebuild N ] dev-lang/gnat-gpl-2021-r5 USE="ada bootstrap cxx fortran nls openmp pie sanitize ssp -cet -d -debug -default-stack-clash-protection -default-znow -doc (-fixed-point) (-go) -graphite -hardened (-jit) -libssp (-lto) -modula2 (-multilib) -objc -objc++ -objc-gc (-pch) -pgo -rust -systemtap -test -vanilla -vtv -zstd"
Created attachment 888325 [details] info.txt emerge info
image: 17.1_no_multilib_systemd_merged_usr-20240319-235702
Reproduced. Just before I was about to log off ;)
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=52fa9d334e23327ba08139f8617d3ae16adff64e commit 52fa9d334e23327ba08139f8617d3ae16adff64e Author: Sam James <sam@gentoo.org> AuthorDate: 2024-03-23 20:18:16 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2024-03-23 20:18:16 +0000 toolchain.eclass: fortify hybrid workaround * Make sure the result is non-empty before trying to use it as an index * Make sure the result is an integer before trying to use it as an index * Don't try to set --param ... if we had no result at all These are good ideas anyway but they happen with gnat-gpl as apparently older GCC didn't actually have the l1-cache-size thing (I thought it was a bit older than 10). Whatever. Closes: https://bugs.gentoo.org/927646 Signed-off-by: Sam James <sam@gentoo.org> eclass/toolchain.eclass | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
