From: Paolo Bonzini <pbonzini@redhat.com>
To: "Thomas Huth" <thuth@redhat.com>,
"Emmanuel Blot" <eblot.ml@gmail.com>,
qemu-devel@nongnu.org,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>
Subject: Re: Meson build on macOS: undefined symbol treatment
Date: Sun, 30 Aug 2020 11:35:17 +0200 [thread overview]
Message-ID: <9b3f88da-ec74-96d0-41a4-8fd89b845a6f@redhat.com> (raw)
In-Reply-To: <24ac4d35-ff2b-4381-ab1b-1a8f31ba36fb@redhat.com>
On 27/08/20 10:16, Thomas Huth wrote:
> Seems like this is added by meson itself (see
> meson/mesonbuild/linkers.py), not by our meson.build files ... Paolo,
> any idea why this happens?
This is done by "b_lundef=false". I think it was added for modules, but
maybe it's not necessary. Emmanuel, can you try removing it (line 3 of
meson.build) and seeing if --enable-modules still works for you?
Paolo
next prev parent reply other threads:[~2020-08-30 9:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 13:11 Meson build on macOS: undefined symbol treatment Emmanuel Blot
2020-08-27 8:16 ` Thomas Huth
2020-08-30 9:35 ` Paolo Bonzini [this message]
2020-08-31 8:12 ` Emmanuel Blot
2020-08-31 10:06 ` Paolo Bonzini
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=9b3f88da-ec74-96d0-41a4-8fd89b845a6f@redhat.com \
--to=pbonzini@redhat.com \
--cc=eblot.ml@gmail.com \
--cc=marcandre.lureau@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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).