On 7/28/23 07:23, Claudio Fontana wrote:
It is a test environment for building packages, so the guest at the time of the
error is running ./configure for the package swig-v4.1.1.tar.gz
checking build system type... s390x-ibm-linux-gnu^M
checking host system type... s390x-ibm-linux-gnu^M
checking for a BSD-compatible install... /usr/bin/install -c^M
checking whether build environment is sane... [New Thread 0x7ffea3fff6c0 (LWP
116436)]
[New Thread 0x7ffec14e26c0 (LWP 116437)]
[New Thread 0x7ffecf73e6c0 (LWP 116438)]
[New Thread 0x7ffecde2c6c0 (LWP 116439)]
[New Thread 0x7ffec2beb6c0 (LWP 116440)]
yes^M
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p^M
checking for gawk... gawk^M
checking whether make sets $(MAKE)... yes^M
checking whether make supports nested variables... yes^M
checking for s390x-ibm-linux-gnu-gcc... gcc^M
checking whether the C compiler works... **
So I presume we are in:
AC_PROG_CC
I am rerunning this over and over, and it seems it always aborts there in the
same place.
You didn't say what the host is, only qemu-system-s390x.
Am I barking up the wrong tree looking at s390x host?
r~
