glibc: Autoconf compilation error

[zokl]

Describe the bug

Compilation of OpenWRT 22.03 GLIBC version - master ends with following error:

ime: toolchain/kernel-headers/compile#0.03#0.02#0.06
make[3]: Entering directory '/mnt/data/ftester/ethershaper_ng/toolchain/glibc/headers'
[ -f /mnt/data/ftester/ethershaper_ng/build_dir/toolchain-x86_64_gcc-12.3.0_glibc/glibc-2.37/.autoconf ] || { cd /mnt/data/ftester/ethershaper_ng/build_dir/toolchain-x86_64_gcc-12.3.0_glibc/glibc-2.37/; autoconf --force && touch /mnt/data/ftester/ethershaper_ng/build_dir/toolchain-x86_64_gcc-12.3.0_glibc/glibc-2.37/.autoconf; }
aclocal.m4:6: error: Exactly version 2.69 of Autoconf is required but you have 2.71
aclocal.m4:6: the top level
autom4te: error: /mnt/data/ftester/ethershaper_ng/staging_dir/host/bin/m4 failed with exit status: 63
make[3]: *** [Makefile:29: /mnt/data/ftester/ethershaper_ng/build_dir/toolchain-x86_64_gcc-12.3.0_glibc/glibc-2.37-headers/.configured] Error 63
make[3]: Leaving directory '/mnt/data/ftester/ethershaper_ng/toolchain/glibc/headers'
time: toolchain/glibc/headers/compile#0.18#0.08#0.27
    ERROR: toolchain/glibc/headers failed to build.
make[2]: *** [toolchain/Makefile:93: toolchain/glibc/headers/compile] Error 1
make[2]: Leaving directory '/mnt/data/ftester/ethershaper_ng'
make[1]: *** [toolchain/Makefile:89: /mnt/data/ftester/ethershaper_ng/staging_dir/toolchain-x86_64_gcc-12.3.0_glibc/stamp/.toolchain_compile] Error 2
make[1]: Leaving directory '/mnt/data/ftester/ethershaper_ng'
make: *** [/mnt/data/ftester/ethershaper_ng/include/toplevel.mk:231: world] Error 2

The propblem is in file aclocal.m4 where is Aclocal version 2.69 defined. Openwrt has Aclocal on version 2.71

OpenWrt version

OpenWRT 22.03 - master branch

OpenWrt target/subtarget

x86_64

Device

PCEngines APU platform

Image kind

Self-built image

Steps to reproduce

Compilation image based on GLIBC.

Actual behaviour

No response

Expected behaviour

No response

Additional info

No response

Diffconfig

No response

Terms

• I am reporting an issue for OpenWrt, not an unsupported fork.

[zokl]

Hi @PolynomialDivision @ynezz do you know how to resolve this issue?