From: Dennis Clarke <dclarke@blastwave.org>
To: qemu-devel@nongnu.org
Subject: FAILED: libqemu-arm-bsd-user.fa.p/bsd-user_signal.c.o
Date: Mon, 10 Oct 2022 06:18:35 +0000 [thread overview]
Message-ID: <af7a54fd-8194-a7fc-cfed-0c8e0cf101a0@blastwave.org> (raw)
On FreeBSD 14.0 CURRENT amd64 everything seems to go swimmingly until :
[5679/6848] Compiling C object libqemu-arm-bsd-user.fa.p/bsd-user_mmap.c.o
[5680/6848] Compiling C object libqemu-arm-bsd-user.fa.p/bsd-user_signal.c.o
FAILED: libqemu-arm-bsd-user.fa.p/bsd-user_signal.c.o
/usr/bin/cc -m64 -mcx16 -Ilibqemu-arm-bsd-user.fa.p -I. -I..
-Itarget/arm -I../target/arm -I../common-user/host/x86_64
-I../bsd-user/include -Ibsd-user/freebsd -I../bsd-user/freebsd
-I../bsd-user/host/x86_64 -Ibsd-user -I../bsd-user -I../bsd-user/arm
-Iqapi -Itrace -Iui -Iui/shader -I/usr/local/include
-I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include
-fcolor-diagnostics -Wall -Winvalid-pch -std=gnu11 -O0 -g -iquote .
-iquote /opt/bw/build/qemu -iquote /opt/bw/build/qemu/include -iquote
/opt/bw/build/qemu/tcg/i386 -pthread -D_GNU_SOURCE
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -Wstrict-prototypes
-Wredundant-decls -Wundef -Wwrite-strings -Wmissing-prototypes
-fno-strict-aliasing -fno-common -fwrapv -Wold-style-definition
-Wtype-limits -Wformat-security -Wformat-y2k -Winit-self
-Wignored-qualifiers -Wempty-body -Wnested-externs -Wendif-labels
-Wexpansion-to-defined -Wno-initializer-overrides
-Wno-missing-include-dirs -Wno-shift-negative-value -Wno-string-plus-int
-Wno-typedef-redefinition -Wno-tautological-type-limit-compare
-Wno-psabi -Wno-gnu-variable-sized-type-not-at-end
-fstack-protector-strong -m64 -g -O0 -fno-builtin -fPIE -DNEED_CPU_H
'-DCONFIG_TARGET="arm-bsd-user-config-target.h"'
'-DCONFIG_DEVICES="arm-bsd-user-config-devices.h"' -MD -MQ
libqemu-arm-bsd-user.fa.p/bsd-user_signal.c.o -MF
libqemu-arm-bsd-user.fa.p/bsd-user_signal.c.o.d -o
libqemu-arm-bsd-user.fa.p/bsd-user_signal.c.o -c ../bsd-user/signal.c
In file included from ../bsd-user/signal.c:27:
In file included from ../bsd-user/host/x86_64/host-signal.h:14:
In file included from /usr/include/vm/pmap.h:92:
/usr/include/machine/pmap.h:452:2: error: fields must have a constant
size: 'variable length array in structure' extension will never be supported
PV_CHUNK_HEADER
^
/usr/include/machine/pmap.h:448:12: note: expanded from macro
'PV_CHUNK_HEADER'
uint64_t pc_map[_NPCM]; /* bitmap; 1 = free */ \
^
/usr/include/machine/pmap.h:456:2: error: fields must have a constant
size: 'variable length array in structure' extension will never be supported
PV_CHUNK_HEADER
^
/usr/include/machine/pmap.h:448:12: note: expanded from macro
'PV_CHUNK_HEADER'
uint64_t pc_map[_NPCM]; /* bitmap; 1 = free */ \
^
2 errors generated.
ninja: build stopped: subcommand failed.
gmake[1]: *** [Makefile:165: run-ninja] Error 1
gmake[1]: Leaving directory '/opt/bw/build/qemu/build'
gmake: *** [GNUmakefile:11: all] Error 2
phobos#
Is there a trivial patch ? Or perhaps try again using GCC and not
LLVM/Clang?
--
Dennis Clarke
RISC-V/SPARC/PPC/ARM/CISC
UNIX and Linux spoken
GreyBeard and suspenders optional
next reply other threads:[~2022-10-10 6:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 6:18 Dennis Clarke [this message]
2022-10-10 7:13 ` FAILED: libqemu-arm-bsd-user.fa.p/bsd-user_signal.c.o Thomas Huth
2022-10-10 17:01 ` Warner Losh
2022-10-13 5:10 ` Warner Losh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=af7a54fd-8194-a7fc-cfed-0c8e0cf101a0@blastwave.org \
--to=dclarke@blastwave.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).