Autoconf image based on Ubuntu 24.04 failed to run WASI CI build

[corona10]

Image: https://github.com/python/cpython-devcontainers/pkgs/container/autoconf/291871937?tag=2024.10.19.11417401087
We notice this issue through python/cpython#122566 (review)
See related Github Action: https://github.com/python/cpython/actions/runs/11421843985/job/31779110126

checking whether float word ordering is bigendian... unknown
configure: error: 

Unknown float word ordering. You need to manually preset
ax_cv_c_float_words_bigendian=no (or yes) according to your system.

 
Traceback (most recent call last):
 File "/home/runner/work/cpython/cpython/Tools/wasm/wasi.py", line 364, in <module>
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯
 main()

cc @brettcannon

[corona10]

cc @erlend-aasland

[erlend-aasland]

The failure is because that PR (python/cpython#122566) changes the CI to use the latest devcontainer. We did actually not switch to that yet (see python/cpython#125571), so you get at least two failures:

• check generated files will fail since there is a mismatch between the autoconf devcontainers used by Tools/build/regen-configure.sh and the autoconf devcontainer in the CI
• the WASI check fails because the autoconf-archive patch does not (yet) work out of the box for us: Configure EXEEXT hacks are interfering with AX_C_FLOAT_WORDS_BIGENDIAN cpython#125698

I'm closing this, since this is already tracked in the following issues:

• Configure EXEEXT hacks are interfering with AX_C_FLOAT_WORDS_BIGENDIAN cpython#125698
• Patch autoconf-archive with an updated variant of AX_C_FLOAT_WORDS_BIGENDIAN #22