On 8/9/26 08:32, John Paul Adrian Glaubitz wrote:
Source: gcc-13 Version: 13.4.0-11 Severity: normal X-Debbugs-Cc: [email protected] User: [email protected] Usertags: alphaHello, on alpha, the gcc-13 build fails because the gnat compiler in the archive is broken. When using an older version of gcc-13 with a working gnat version, the build succeeds but fails when checking ALIHASH: echo "checking ALIHASH ..."; \ p=gnat-13-alpha-linux-gnu; \ old=$(apt-cache show $p | awk '/^Provides/ {print $2}'); \ new=gnat-13-$(debian/ada/libgnat_alihash | sed 's/.*=//'); \ if [ $old = $new ]; then \ echo " -> matching alihash ($old)"; \ else \ echo " -> alihash mismatch: $old (installed), $new (built)"; \ if [ xyes = xyes ]; then \ exit 1; \ fi; \ fi checking ALIHASH ... /bin/bash: line 5: [: too many arguments -> alihash mismatch: gnat-13-119f978a gnat-13-97e8392b (installed), gnat-13-119f978a (built) make[1]: *** [debian/rules2:1400: stamps/05-build-stamp] Error 1 make[1]: Leaving directory '/home/glaubitz/gcc-13-new/gcc-13-13.4.0' make: *** [debian/rules:53: build-arch] Error 2 I have no idea what that hash value exactly means, but the bash syntax error during the check looks suspicious, so I decided to report a bug. FWIW, the build fully succeeds when disabling the check. I used this, to build gcc-13_13.4.0-11 for alpha and then tried a fresh local build where again the ALIHASH check failed.
that is fixed in the VCS. I don't plan any updates before the 13.5. release.
