On 5/25/22 19:34, Ryan Long wrote:
On 5/24/2022 5:32 PM, Chris Johns wrote:
On 25/5/2022 12:47 am, Ryan Long wrote:
When building QEMU it goes through the entire build and it looks like
it passes,
but it is failing. The only error that Joel and I saw in the output
was this
Found ninja-1.10.1 at /usr/bin/ninja
+
LD_LIBRARY_PATH=/home/tester/rtems-cron-6/rtems-source-builder/bare/build/tmp/sb-1002/devel/qemu/home/tester/rtems-cron-6/tools/6/lib
make -j 8 all
/usr/bin/ninja build.ninja && touch build.ninja.stamp
ninja: no work to do.
/usr/bin/python3 -B
/home/tester/rtems-cron-6/rtems-source-builder/bare/build/qemu-5.2.0-rc1-x86_64-linux-gnu-1/qemu-5.2.0-rc1/meson/meson.py
introspect --targets --tests --benchmarks | /usr/bin/python3 -B
scripts/mtest2make.py > Makefile.mtest
BUILD multiboot.img
BUILD linuxboot.img
BUILD linuxboot_dma.img
BUILD kvmvapic.img
ld: Error: unable to disambiguate: -no-pie (did you mean --no-pie ?)
ld: Error: unable to disambiguate: -no-pie (did you mean --no-pie ?)
Unless someone has any objections, I'm going to try the 5.2.0
release, and if
that doesn't work, I'm going to try bumping it to 6.2.0.
Which hosts are you testing builds on?
We have
- Ubuntu 21.04
Ubuntu 20.04.x LTS up-to-date.
building: qemu-5.2.0-rc1-x86_64-linux-gnu-1
sizes: qemu-5.2.0-rc1-x86_64-linux-gnu-1: 8.129GB (installed: 903.642MB)
cleaning: qemu-5.2.0-rc1-x86_64-linux-gnu-1
reporting: devel/qemu-5.2.0-1.cfg -> qemu-5.2.0-rc1-x86_64-linux-gnu-1.txt
reporting: devel/qemu-5.2.0-1.cfg -> qemu-5.2.0-rc1-x86_64-linux-gnu-1.xml
installing: gettext-0.18.3.1-x86_64-linux-gnu-1 -> /tmp/qemu
installing: libffi-3.0.13-x86_64-linux-gnu-1 -> /tmp/qemu
installing: pixman-0.40.0-x86_64-linux-gnu-1 -> /tmp/qemu
installing: glib-2.48.2-x86_64-linux-gnu-1 -> /tmp/qemu
installing: qemu-5.2.0-rc1-x86_64-linux-gnu-1 -> /tmp/qemu
cleaning: gettext-0.18.3.1-x86_64-linux-gnu-1
cleaning: libffi-3.0.13-x86_64-linux-gnu-1
cleaning: pixman-0.40.0-x86_64-linux-gnu-1
cleaning: glib-2.48.2-x86_64-linux-gnu-1
cleaning: qemu-5.2.0-rc1-x86_64-linux-gnu-1
Build Sizes: usage: 9.084GB total: 1.083GB (sources: 131.649MB, patches:
24.060KB, installed 977.773MB)
Build Set: Time 0:19:01.870883
The part you see problematic above looks as follows here:
BUILD multiboot.img
BUILD linuxboot_dma.img
BUILD linuxboot.img
BUILD kvmvapic.img
BUILD linuxboot_dma.raw
BUILD multiboot.raw
BUILD linuxboot.raw
BUILD kvmvapic.raw
SIGN linuxboot_dma.bin
SIGN multiboot.bin
SIGN linuxboot.bin
SIGN kvmvapic.bin
BUILD pvh.img
BUILD pvh.raw
SIGN pvh.bin
[1/8300] Compiling C object libcapstone.a.p/capstone_MCInstrDesc.c.o
[2/8300] Compiling C object libcapstone.a.p/capstone_utils.c.o
[3/8300] Compiling C object libcapstone.a.p/capstone_MCRegisterInfo.c.o
[4/8300] Compiling C object
libcapstone.a.p/capstone_arch_PowerPC_PPCModule.c.o
[5/8300] Compiling C object libcapstone.a.p/capstone_MCInst.c.o
[6/8300] Compiling C object libcapstone.a.p/capstone_SStream.c.o
[7/8300] Compiling C object
libcapstone.a.p/capstone_arch_PowerPC_PPCMapping.c.o
[8/8300] Compiling C object libcapstone.a.p/capstone_arch_ARM_ARMModule.c.o
[9/8300] Compiling C object
libcapstone.a.p/capstone_arch_AArch64_AArch64BaseInfo.c.o
[10/8300] Compiling C object
libcapstone.a.p/capstone_arch_SystemZ_SystemZMCTargetDesc.c.o
[11/8300] Compiling C object
libcapstone.a.p/capstone_arch_AArch64_AArch64Module.c.o
[12/8300] Compiling C object
libcapstone.a.p/capstone_arch_SystemZ_SystemZModule.c.o
[...]
- FreeBSD 12.2 and 13
- QEMU doesn't build on either of these for me either
Here I have 13.1 and it's also able to build qemu -- except the images.
But binaries looks fine.
- macOS (Big Sur)
- I don't think QEMU built on here, but I can't get into the VM at
the moment
Indeed, last time I tested on Catalina I was not able to build qemu
there either.
Karel
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
