From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Amol Surati <suratiamol@gmail.com>, berrange@redhat.com
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] qemu compilation failure with nettle 3.5.1
Date: Thu, 11 Jul 2019 13:18:17 +0100 [thread overview]
Message-ID: <20190711121817.GB5846@work-vm> (raw)
In-Reply-To: <20190711052608.GA2619@arch>
Copying in Daniel
* Amol Surati (suratiamol@gmail.com) wrote:
> Hi,
>
> The qemu upstream (at commit 6df2cdf44a at the moment) fails to compile
> with nettle 3.5.1. It seems that Nettle has deprecated a few parts of
> its API.
>
> A workaround is to provide --disable-nettle during qemu configuration.
>
> A portion of the error log:
>
> error: ‘nettle_aes_encrypt’ is deprecated
> error: ‘nettle_aes_decrypt’ is deprecated
> error: ‘nettle_aes_encrypt’ is deprecated
> error: ‘nettle_aes_decrypt’ is deprecated
> error: ‘nettle_aes_set_encrypt_key’ is deprecated
> error: ‘nettle_aes_set_decrypt_key’ is deprecated
> error: ‘nettle_aes_set_encrypt_key’ is deprecated
> error: ‘nettle_aes_set_decrypt_key’ is deprecated
> error: ‘nettle_aes_set_encrypt_key’ is deprecated
> error: ‘nettle_aes_set_decrypt_key’ is deprecated
>
>
> The declaration of one of the functions from nettle's aes.h:
>
> void
> aes_encrypt(const struct aes_ctx *ctx,
> size_t length, uint8_t *dst,
> const uint8_t *src) _NETTLE_ATTRIBUTE_DEPRECATED;
>
> Thanks,
> Amol
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2019-07-11 12:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 5:26 [Qemu-devel] qemu compilation failure with nettle 3.5.1 Amol Surati
2019-07-11 12:18 ` Dr. David Alan Gilbert [this message]
2019-07-11 13:03 ` 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=20190711121817.GB5846@work-vm \
--to=dgilbert@redhat.com \
--cc=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=suratiamol@gmail.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).