On 6/2/25 2:11 PM, Cédric Le Goater wrote:
On 6/2/25 22:53, Nabih Estefan wrote:
Hi Pierrick,
For what it's worth, those files were also breaking on Ubuntu and Debian for me.
I had to explicitly `sudo apt install libfdt-dev` for it to work
again. I don't believe
it was installed at all previously, but QEMU was building and working correctly
without it being explicitly installed.
yes. I had to install libfdt-dev/el on some systems too.
However, for the windows (on Linux) build :
./configure --cross-prefix=x86_64-w64-mingw32-
--target-list=aarch64-softmmu,ppc64-softmmu,x86_64-softmmu,s390x-softmmu
--disable-docs --disable-sdl
Thanks Cédric, I could reproduce it using the fedora-win64-cross
container. After investigation, it's related to having a target-list,
and in a specific order (hum, hum, feels bad). I observe the same
behaviour when building normally for Linux too.
Those 3 commands work as expected:
$ ./configure --target-list=aarch64-softmmu && \
ninja -C build libsystem_arm.a.p/hw_arm_raspi4b.c.o
$ ./configure && \
ninja -C build libsystem_arm.a.p/hw_arm_raspi4b.c.o
$ ./configure --target-list=s390x-softmmu,aarch64-softmmu && \
ninja -C build libsystem_arm.a.p/hw_arm_raspi4b.c.o
This one fails:
$ ./configure --target-list=aarch64-softmmu,s390x-softmmu && \
ninja -C build libsystem_arm.a.p/hw_arm_raspi4b.c.o
I will investigate more, but I strongly suspect there is a bug in the
meson libraries patch I wrote, with a variable being reused when it
should not.
Sorry for the inconvenience.
Regards,
Pierrick
