From: "Daniel P. Berrange" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Eric Blake <eblake@redhat.com>,
Programmingkid <programmingkidx@gmail.com>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] undefined symbol _nettle_cast5_set_key
Date: Tue, 31 May 2016 10:18:45 +0100 [thread overview]
Message-ID: <20160531091845.GG21628@redhat.com> (raw)
In-Reply-To: <CAFEAcA_XGyq5MSuhhx4d241RbqL2+c_G6f3pQbVQHArXfarFzw@mail.gmail.com>
On Sat, May 21, 2016 at 02:14:07PM +0100, Peter Maydell wrote:
> On 20 May 2016 at 23:43, Eric Blake <eblake@redhat.com> wrote:
> > What version of nettle are you compiling against? Obviously it's an
> > older version, but is it one that we need to work around at configure
> > time, or one that you should just update locally?
>
> I think in general if we can't build against a version of
> a library dependency we should always disable the relevant
> optional feature at compile time -- this just makes life easier
> for users, since updating a library (or removing it) isn't always
> possible.
Absolutely, I'll be looking into this issue now I'm back from vacation.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2016-05-31 9:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 19:15 [Qemu-devel] undefined symbol _nettle_cast5_set_key Programmingkid
2016-05-20 22:43 ` Eric Blake
2016-05-20 22:46 ` Programmingkid
2016-05-20 22:50 ` Eric Blake
2016-05-20 23:04 ` Programmingkid
2016-05-21 13:14 ` Peter Maydell
2016-05-21 14:18 ` Programmingkid
2016-05-31 9:18 ` Daniel P. Berrange [this message]
2016-05-31 14:00 ` Daniel P. Berrange
2016-05-31 14:25 ` Programmingkid
2016-05-31 14:51 ` Daniel P. Berrange
2016-05-31 15:48 ` Programmingkid
2016-05-31 16:00 ` Daniel P. Berrange
2016-06-02 17:01 ` Programmingkid
2016-06-02 17:06 ` Daniel P. Berrange
2016-06-03 14:02 ` Programmingkid
2016-05-31 14:36 ` 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=20160531091845.GG21628@redhat.com \
--to=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=programmingkidx@gmail.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 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).