From: Eric Blake <eblake@redhat.com>
To: Programmingkid <programmingkidx@gmail.com>
Cc: qemu-devel qemu-devel <qemu-devel@nongnu.org>,
"Daniel P. Berrange" <berrange@redhat.com>
Subject: Re: [Qemu-devel] undefined symbol _nettle_cast5_set_key
Date: Fri, 20 May 2016 16:50:59 -0600 [thread overview]
Message-ID: <573F94D3.7090902@redhat.com> (raw)
In-Reply-To: <2C42DD54-A6FC-47F8-B4D3-33E7A7413068@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 907 bytes --]
On 05/20/2016 04:46 PM, Programmingkid wrote:
>>> Undefined symbols for architecture x86_64:
>>> "_nettle_cast5_set_key", referenced from:
>>> _qcrypto_cipher_new in cipher.o
>>
>> 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'm not sure how to find the version of nettle. Would you have a simple program that could tell me this information?
On Fedora, it's:
# rpm -q nettle-devel
nettle-devel-3.2-1.fc23.x86_64
# pkg-config --modversion nettle
3.2
I don't use MacOS, so I have no clue how to query your package manager
about what version of a given package is installed, but the pkg-config
command might work.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2016-05-20 22:51 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 [this message]
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
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=573F94D3.7090902@redhat.com \
--to=eblake@redhat.com \
--cc=berrange@redhat.com \
--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 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.