From: David Edmondson <dme@dme.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: Alexey Krasikov <alex-krasikov@yandex-team.ru>
Subject: Re: [PULL 3/5] crypto/linux_keyring: add 'secret_keyring' secret object.
Date: Tue, 16 Jun 2020 17:49:47 +0100 [thread overview]
Message-ID: <m2y2on6jmc.fsf@dme.org> (raw)
In-Reply-To: <20200615103633.300208-4-berrange@redhat.com>
On Monday, 2020-06-15 at 11:36:31 +01, Daniel P. Berrangé wrote:
> +if test "$secret_keyring" != "no"
> +then
> + if test "$have_keyring" == "yes"
This generates a complaint when building on Debian testing:
./configure: 6319: test: yes: unexpected operator
Perhaps should be a single = ?
> + then
> + secret_keyring=yes
> + else
> + if test "$secret_keyring" = "yes"
> + then
> + error_exit "syscall __NR_keyctl requested, \
> +but not implemented on your system"
> + else
> + secret_keyring=no
> + fi
> + fi
> +fi
> +
dme.
--
The sound of a barking dog on a loop, a plane rises in the crystal blue.
next prev parent reply other threads:[~2020-06-16 16:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 10:36 [PULL v2 0/5] Qcrypto next patches Daniel P. Berrangé
2020-06-15 10:36 ` [PULL 1/5] crypto: add "none" random provider Daniel P. Berrangé
2020-06-15 10:36 ` [PULL 2/5] crypto/secret: move main logic from 'secret' to 'secret_common' Daniel P. Berrangé
2020-06-15 10:36 ` [PULL 3/5] crypto/linux_keyring: add 'secret_keyring' secret object Daniel P. Berrangé
2020-06-16 16:49 ` David Edmondson [this message]
2020-06-16 16:51 ` Daniel P. Berrangé
2020-06-15 10:36 ` [PULL 4/5] test-crypto-secret: add 'secret_keyring' object tests Daniel P. Berrangé
2020-06-15 10:36 ` [PULL 5/5] crypto: Remove use of GCRYPT_VERSION macro Daniel P. Berrangé
2020-06-16 9:03 ` [PULL v2 0/5] Qcrypto next patches Peter Maydell
-- strict thread matches above, loose matches on Subject: below --
2020-05-29 10:35 [PULL " Daniel P. Berrangé
2020-05-29 10:35 ` [PULL 3/5] crypto/linux_keyring: add 'secret_keyring' secret object Daniel P. Berrangé
2020-06-05 11:06 ` 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=m2y2on6jmc.fsf@dme.org \
--to=dme@dme.org \
--cc=alex-krasikov@yandex-team.ru \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.