All of lore.kernel.org
 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] [PULL v1 0/4] Misc fixes for crypto code module
Date: Thu, 22 Oct 2015 11:13:33 +0100	[thread overview]
Message-ID: <20151022101333.GE9079@redhat.com> (raw)
In-Reply-To: <CAFEAcA-JbiheuSzZWf3dNuYeNMCc3M3C9SyRmRKRKATfvnYnSg@mail.gmail.com>

On Wed, Oct 21, 2015 at 09:21:05PM +0100, Peter Maydell wrote:
> On 21 October 2015 at 11:47, Daniel P. Berrange <berrange@redhat.com> wrote:
> > The following changes since commit ee9dfed242610ecb91418270fd46b875ed56e201:
> >
> >   Merge remote-tracking branch 'remotes/kraxel/tags/pull-input-20151020-1' into staging (2015-10-20 12:56:45 +0100)
> >
> > are available in the git repository at:
> >
> >   https://github.com/berrange/qemu.git tags/qcrypto-fixes-pull-20151021-1
> >
> > for you to fetch changes up to 635b2807565e0724e4aed73f8ca54f14df051499:
> >
> >   configure: avoid polluting global CFLAGS with tasn1 flags (2015-10-21 11:42:42 +0100)
> >
> > ----------------------------------------------------------------
> > Merge qcrypto-fixes 2015/10/21
> >
> > ----------------------------------------------------------------
> 
> Hi. I'm afraid this fails to build on w32:
> 
> /home/petmay01/linaro/qemu-for-merges/crypto/init.c:30:20: error:
> gcrypt.h: No such file or directory
> /home/petmay01/linaro/qemu-for-merges/crypto/init.c:108: error:
> variable ‘qcrypto_gcrypt_thread_impl’ has initializer but incomplete
> type
> /home/petmay01/linaro/qemu-for-merges/crypto/init.c:109: error:
> ‘GCRY_THREAD_OPTION_PTHREAD’ undeclared here (not in a function)
> /home/petmay01/linaro/qemu-for-merges/crypto/init.c:109: error:
> ‘GCRY_THREAD_OPTION_VERSION’ undeclared here (not in a function)
> 
> (and then a large pile of other errors that you'd expect from
> failing to find gcrypt.h.)

Oh, fun, a pre-existing bug in configure, which we now trigger more
often. We look for 'libgcrypt-config' in $PATH, but don't bother to
check whether the one we found is for native builds or cross builds.
I'll fix configure to run 'libgcrypt-config --host' to make sure
we match the cross prefix.

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 10:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21 10:47 [Qemu-devel] [PULL v1 0/4] Misc fixes for crypto code module Daniel P. Berrange
2015-10-21 10:47 ` [Qemu-devel] [PULL v1 1/4] crypto: allow use of nettle/gcrypt to be selected explicitly Daniel P. Berrange
2015-10-21 10:47 ` [Qemu-devel] [PULL v1 2/4] crypto: don't let builtin aes crash if no IV is provided Daniel P. Berrange
2015-10-21 10:47 ` [Qemu-devel] [PULL v1 3/4] crypto: add sanity checking of plaintext/ciphertext length Daniel P. Berrange
2015-10-21 10:47 ` [Qemu-devel] [PULL v1 4/4] configure: avoid polluting global CFLAGS with tasn1 flags Daniel P. Berrange
2015-10-21 20:21 ` [Qemu-devel] [PULL v1 0/4] Misc fixes for crypto code module Peter Maydell
2015-10-22 10:13   ` Daniel P. Berrange [this message]

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=20151022101333.GE9079@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 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.