From: Thomas Huth <thuth@redhat.com>
To: Dennis Clarke <dclarke@blastwave.org>, qemu-devel@nongnu.org
Cc: "Volker Rümelin" <vr_qemu@t-online.de>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Warner Losh" <imp@bsdimp.com>
Subject: Re: total fail on FreeBSD 14.0 amd64 regardless of compiler
Date: Mon, 10 Oct 2022 09:21:51 +0200 [thread overview]
Message-ID: <e84ed09e-78c4-ac7c-19ef-f53ede3330e4@redhat.com> (raw)
In-Reply-To: <841ab433-7dcd-2cf3-de7a-eb8b890f1652@blastwave.org>
On 10/10/2022 08.56, Dennis Clarke wrote:
>
> re: https://lists.nongnu.org/archive/html/qemu-devel/2022-10/msg01249.html
>
> Using GCC 12 is even worse :
>
> [2040/6841] Compiling C object qemu-system-aarch64.p/softmmu_main.c.o
> [2041/6841] Linking target qemu-system-aarch64
> FAILED: qemu-system-aarch64
> /usr/local/bin/g++12 -m64 -mcx16 @qemu-system-aarch64.rsp
> /usr/local/bin/ld: libqemuutil.a.p/util_filemonitor-inotify.c.o: undefined
> reference to symbol 'inotify_init1'
Now that sounds like the detection for inotify_init1 did not work
right in the meson.build script...
Looking at meson.build:
config_host_data.set('CONFIG_INOTIFY1',
cc.has_header_symbol('sys/inotify.h', 'inotify_init1'))
... do you have such a "inotify.h" header on your FreeBSD system
and does it contain an inotify_init1 function?
Thomas
next prev parent reply other threads:[~2022-10-10 7:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 6:56 total fail on FreeBSD 14.0 amd64 regardless of compiler Dennis Clarke
2022-10-10 7:21 ` Thomas Huth [this message]
2022-10-10 7:28 ` Dennis Clarke
2022-10-10 9:04 ` Daniel P. Berrangé
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=e84ed09e-78c4-ac7c-19ef-f53ede3330e4@redhat.com \
--to=thuth@redhat.com \
--cc=dclarke@blastwave.org \
--cc=imp@bsdimp.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vr_qemu@t-online.de \
/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).