Follow-up Comment #2, sr #110687 (project autoconf):
> It appears to me that this is an issue with cross compilation and strict
conformance mode (-std=c11), not with -flto. Could you please report what
happens, using the same cross-compilation toolchain, if you run the same
configure command but using CFLAGS="-std=c11" LDFLAGS="" ?
In that case (only -std=c11) everything works as expected.
checking for unistd.h... yes
checking whether byte ordering is bigendian... no
configure: creating ./config.status
config.status: creating issue618config.h
The issue only occurs when using -flto.
> It would also be helpful to know which C library is in use in the target
environment, and its version number.
The system is Ubuntu 22.04. glibc 2.35. The cross-compiler is
aarch64-linux-gnu-g++ (Ubuntu 11.2.0-17ubuntu1) 11.2.0.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?110687>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
