qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] configure claims I requested feature nettle when I didn't...
Date: Thu, 22 Oct 2015 16:43:04 +0100	[thread overview]
Message-ID: <20151022154304.GK9079@redhat.com> (raw)
In-Reply-To: <CAFEAcA93p4A4dgL7Rg-VPytciDtYd9gWJS5DJHQG6_dSwsUz3A@mail.gmail.com>

On Thu, Oct 22, 2015 at 04:17:10PM +0100, Peter Maydell wrote:
> [pm215@gcc1-power7 all]$ ../../configure
> ERROR: User requested feature nettle
>        configure was not able to find it.
>        Install nettle devel
> 
> ...but as you can see I didn't ask for nettle explicitly at all,
> so configure should fall back to disabling it, not exiting with
> an error.
> 
> configure --disable-gnutls seems to work around this. I think
> what is happening is that the logic to check for gnutls is
> deciding that gnutls exists and so it can set the feature to
> yes, but is failing to fall back to "actually, no" if the
> user didn't explicitly require gnutls and gnutls needs nettle
> and nettle isn't installed.

Yes, if configure finds  gnutls, it tries to figure out if gnutls
links to nettle or gcrypt, and then checks for the corresponding
one. It fails if gnutls is found, but the corresponding nettle/gcrypt
is not found, on the basis that that should not actually happen, as
installing gnutls-dev should pull in nettle-dev/gcrypt-dev packages
as appropriate.

Did you only see this with todays master ?  This particular hard failure
logic was present even before commit 4e2abbeacce6e12e62a0183c67936c807b19c3b9
so I would expect you to see it all the way back to
ed754746fea55df726f4de3dadb5bea0b6aa7409

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 :|

  reply	other threads:[~2015-10-22 15:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-22 15:17 [Qemu-devel] configure claims I requested feature nettle when I didn't Peter Maydell
2015-10-22 15:43 ` Daniel P. Berrange [this message]
2015-10-22 16:09   ` Peter Maydell
2015-10-22 16:11     ` Daniel P. Berrange

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=20151022154304.GK9079@redhat.com \
    --to=berrange@redhat.com \
    --cc=peter.maydell@linaro.org \
    --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).