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: Paolo Bonzini <pbonzini@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL v3 00/12] Final changes for 2.4-rc0
Date: Fri, 24 Jul 2015 14:10:02 +0100	[thread overview]
Message-ID: <20150724131002.GM6880@redhat.com> (raw)
In-Reply-To: <CAFEAcA-ojp-9kTocUTJnfP8W4b01zQxS-2Ew9TY7UXGkzwhSNQ@mail.gmail.com>

On Fri, Jul 24, 2015 at 02:06:44PM +0100, Peter Maydell wrote:
> On 24 July 2015 at 14:00, Peter Maydell <peter.maydell@linaro.org> wrote:
> > On 24 July 2015 at 13:53, Paolo Bonzini <pbonzini@redhat.com> wrote:
> >> Ok, then it looks like a preexisting problem indeed.
> >
> > Well, not entirely. This set of configure flags used to work,
> > and now it does not. That's a regression.
> 
> In particular, configure --static --disable-tools --disable-system
> now fails, and I think that's a perfectly sensible set of options.

Presumably you have previously figured out which static libs you
needed to install on your build machine previously though ?
As that command line fails to verify presence of any static
libraries at all - configure doesn't stop and tell me to install
any static libraries at all on my machine which has no static
libs present - it just fails to build later

> 
> It fails trying to link
>   LINK  tests/qemu-iotests/socket_scm_helper:
> 
> ...why are we trying to build a helper program in tests/ for
> a simple 'make' (not 'make check') ? Why are we building it
> in a config which has disabled building tools and system exes?
> 
> Probably avoiding building this random exe would fix things.

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

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-08 11:19 [Qemu-devel] [PULL v3 00/12] Final changes for 2.4-rc0 Paolo Bonzini
2015-07-08 14:46 ` Peter Maydell
2015-07-08 15:21   ` Paolo Bonzini
2015-07-08 15:48     ` Peter Maydell
2015-07-08 17:06       ` Paolo Bonzini
2015-07-08 18:03         ` Peter Maydell
2015-07-24 12:52       ` Daniel P. Berrange
2015-07-24 12:53         ` Paolo Bonzini
2015-07-24 13:00           ` Peter Maydell
2015-07-24 13:02             ` Paolo Bonzini
2015-07-24 13:06             ` Peter Maydell
2015-07-24 13:10               ` Daniel P. Berrange [this message]
2015-07-24 13:31                 ` Peter Maydell
2015-07-24 13:48                   ` Daniel P. Berrange
2015-07-24 13:50                     ` Paolo Bonzini
2015-07-24 13:55                   ` Paolo Bonzini
2015-07-24 14:14                     ` Daniel P. Berrange
2015-07-24 14:15                       ` Paolo Bonzini
2015-07-24 14:19                         ` Daniel P. Berrange
2015-07-24 14:21                           ` Paolo Bonzini
2015-07-24 14:25                     ` Peter Maydell
2015-07-24 15:09                       ` Peter Maydell
2015-07-08 20:48 ` Peter Maydell
2015-07-09  7:02   ` Paolo Bonzini

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=20150724131002.GM6880@redhat.com \
    --to=berrange@redhat.com \
    --cc=pbonzini@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.