From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philippe.mathieu.daude@gmail.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org,
Richard Henderson <richard.henderson@linaro.org>
Subject: Re: [PATCH for-7.0] meson.build: Fix dependency of page-vary-common.c to config-poison.h
Date: Wed, 30 Mar 2022 14:24:21 +0200 [thread overview]
Message-ID: <7eb70fcb-0010-f291-6361-b270615ed7ef@redhat.com> (raw)
In-Reply-To: <e4de3f54-e812-9393-0b13-504fb78063e2@gmail.com>
On 30/03/2022 14.05, Philippe Mathieu-Daudé wrote:
> Hi Thomas,
>
> On 30/3/22 13:48, Thomas Huth wrote:
>> Before compiling page-vary-common.c, we have to make sure that
>> config-poison.h has been generated (which is in the "genh" list).
>
> I am a bit confused, "config-poison.h" is include by "exec/poison.h"
> which is included by "qemu/osdep.h" for all non-softmmu code (tools,
> common and -user).
>
> Why is pagevary specific?
pagevary is certainly not specific here, we're doing this
all over the place in meson.build:
$ grep -r static_library.*genh meson.build
libmodulecommon = static_library('module-common', files('module-common.c') + genh, pic: true, c_args: '-DBUILD_DSO')
pagevary = static_library('page-vary-common', sources: pagevary + genh,
sl = static_library(d + '-' + m, [genh, module_ss.sources()],
libqom = static_library('qom', qom_ss.sources() + genh,
libauthz = static_library('authz', authz_ss.sources() + genh,
libcrypto = static_library('crypto', crypto_ss.sources() + genh,
libio = static_library('io', io_ss.sources() + genh,
libmigration = static_library('migration', sources: migration_files + genh,
libblock = static_library('block', block_ss.sources() + genh,
libblockdev = static_library('blockdev', blockdev_ss.sources() + genh,
libqmp = static_library('qmp', qmp_ss.sources() + genh,
libchardev = static_library('chardev', chardev_ss.sources() + genh,
libhwcore = static_library('hwcore', sources: hwcore_ss.sources() + genh,
> Shouldn't add genh to all common_ss[]?
>
> Maybe the problem is how common_all[] is created?
Maybe there is a better way to handle these dependencies ...
but that's rather a bigger change and thus something for
the 7.1 cycle, I think.
Thomas
>> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/948
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>> meson.build | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/meson.build b/meson.build
>> index aef724ad3c..04ce33fef1 100644
>> --- a/meson.build
>> +++ b/meson.build
>> @@ -2881,7 +2881,7 @@ if get_option('b_lto')
>> if get_option('cfi')
>> pagevary_flags += '-fno-sanitize=cfi-icall'
>> endif
>> - pagevary = static_library('page-vary-common', sources: pagevary,
>> + pagevary = static_library('page-vary-common', sources: pagevary + genh,
>> c_args: pagevary_flags)
>> pagevary = declare_dependency(link_with: pagevary)
>> endif
>
next prev parent reply other threads:[~2022-03-30 12:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-30 11:48 [PATCH for-7.0] meson.build: Fix dependency of page-vary-common.c to config-poison.h Thomas Huth
2022-03-30 12:05 ` Philippe Mathieu-Daudé
2022-03-30 12:24 ` Thomas Huth [this message]
2022-03-30 15:03 ` Paolo Bonzini
2022-03-30 14:14 ` Richard Henderson
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=7eb70fcb-0010-f291-6361-b270615ed7ef@redhat.com \
--to=thuth@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philippe.mathieu.daude@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=richard.henderson@linaro.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).