From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"open list:Block layer core" <qemu-block@nongnu.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Max Reitz" <mreitz@redhat.com>,
"Roman Bolshakov" <r.bolshakov@yadro.com>,
"Gerd Hoffmann" <kraxel@redhat.com>
Subject: Re: [PATCH] meson: Propagate gnutls dependency
Date: Mon, 4 Jan 2021 18:49:30 +0100 [thread overview]
Message-ID: <b9198e6f-fba6-921d-4530-dc257064809e@redhat.com> (raw)
In-Reply-To: <CAFEAcA8e916+AU4Ebvie504AOoOBP8wZ8rC90=Hcws76wpkMTQ@mail.gmail.com>
On 04/01/21 16:19, Peter Maydell wrote:
> On Mon, 4 Jan 2021 at 14:40, Paolo Bonzini <pbonzini@redhat.com> wrote:
>>
>> On 04/01/21 14:21, Peter Maydell wrote:
>>>> The rest of QEMU should only ever be using QEMU's TLS abstractions
>>>> and not directly be tied to GNUTLS. So ideally the gnutls flags
>>>> should only ever be added in the crypto/meson.build, and anything
>>>> which depends on that should then get the flags indirectly.
>>> Unfortunately include/crypto/tlscreds.h leaks this implementation
>>> detail
>>
>> That is not a problem. As Daniel said, anything depending on crypto can
>> still get the gnutls flags _indirectly_.
>>
>> In my proposed solution to the bug you'd get that via
>>
>> io_ss.add(crypto, qom)
>> libio = static_library(..., dependencies: io_ss.dependencies())
>
> Does this work recursively? For instance monitor/qmp-cmds.c
> needs the gnutls CFLAGS because:
> * qmp-cmds.c includes ui/vnc.h
> * ui/vnc.h includes include/crypto/tlssession.h
> * include/crypto/tlssession.h includes gnutls.h
>
> I don't see anything in monitor/meson.build that says "qmp-cmds.c
> needs whatever ui's dependencies are".
Hmm, I would have thought it would be handled, but Roman said otherwise.
I'll look into it, at worst we can fix Meson and temporarily apply
Roman's patch until it makes it into a release.
Paolo
next prev parent reply other threads:[~2021-01-04 17:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-02 12:52 [PATCH] meson: Propagate gnutls dependency Roman Bolshakov
2021-01-02 13:25 ` Peter Maydell
2021-01-02 14:16 ` Roman Bolshakov
2021-01-02 19:43 ` Paolo Bonzini
2021-01-04 17:24 ` Roman Bolshakov
2021-01-04 20:50 ` Paolo Bonzini
2021-01-05 14:37 ` Roman Bolshakov
2021-01-05 17:41 ` Paolo Bonzini
2021-01-07 11:41 ` Paolo Bonzini
2021-01-07 15:56 ` Roman Bolshakov
2021-01-07 16:23 ` Paolo Bonzini
2021-01-07 18:18 ` Roman Bolshakov
2021-01-07 18:22 ` Paolo Bonzini
2021-01-07 19:36 ` Roman Bolshakov
2021-01-07 19:41 ` Paolo Bonzini
2021-01-08 19:29 ` Roman Bolshakov
2021-01-08 20:02 ` Paolo Bonzini
2021-01-04 12:21 ` Daniel P. Berrangé
2021-01-04 12:30 ` Paolo Bonzini
2021-01-04 13:21 ` Peter Maydell
2021-01-04 14:40 ` Paolo Bonzini
2021-01-04 15:19 ` Peter Maydell
2021-01-04 17:49 ` Paolo Bonzini [this message]
2021-01-04 17:51 ` Peter Maydell
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=b9198e6f-fba6-921d-4530-dc257064809e@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=r.bolshakov@yadro.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).