From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: Juan Quintela <quintela@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH] test: Fix test-crypto-secret when compiling without keyring support
Date: Fri, 3 Mar 2023 13:00:08 +0000 [thread overview]
Message-ID: <ZAHvWGvHLXp1OLL5@redhat.com> (raw)
In-Reply-To: <029b545a-e814-5917-0a3f-edc578844dbe@redhat.com>
On Fri, Mar 03, 2023 at 01:47:40PM +0100, Thomas Huth wrote:
> On 01/03/2023 12.00, Juan Quintela wrote:
> > Linux keyring support is protected by CONFIG_KEYUTILS.
> > Use CONFIG_SECRET_KEYRING.
> >
> > Signed-off-by: Juan Quintela <quintela@redhat.com>
> >
> > ---
> >
> > Previous version of this patch changed the meson build rules.
> > Daniel told me that the proper fix was to change the #ifdef test.
> > ---
> > tests/unit/test-crypto-secret.c | 10 +++++-----
> > 1 file changed, 5 insertions(+), 5 deletions(-)
>
> This seems to cause failures in the CI:
>
> https://gitlab.com/thuth/qemu/-/jobs/3870672310#L1443
> https://gitlab.com/thuth/qemu/-/jobs/3870672331#L2353
>
> ../tests/unit/test-crypto-secret.c:29:10: fatal error: keyutils.h: No such file or directory
> 29 | #include <keyutils.h>
> | ^~~~~~~~~~~~
> compilation terminated.
Hmm, so we actually have to test for both #ifdefs then
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2023-03-03 13:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 11:00 [PATCH] test: Fix test-crypto-secret when compiling without keyring support Juan Quintela
2023-03-01 11:07 ` Daniel P. Berrangé
2023-03-03 12:47 ` Thomas Huth
2023-03-03 13:00 ` Daniel P. Berrangé [this message]
2023-03-03 19:40 ` Juan Quintela
2023-03-03 19:03 ` Juan Quintela
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=ZAHvWGvHLXp1OLL5@redhat.com \
--to=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--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).