On Fri, Jul 24, 2015 at 02:31:12PM +0100, Peter Maydell wrote: > On 24 July 2015 at 14:10, Daniel P. Berrange <berra...@redhat.com> wrote: > > On Fri, Jul 24, 2015 at 02:06:44PM +0100, Peter Maydell wrote: > >> On 24 July 2015 at 14:00, Peter Maydell <peter.mayd...@linaro.org> wrote: > >> > On 24 July 2015 at 13:53, Paolo Bonzini <pbonz...@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 > > Yes, but the set of required static libs for linux-user is pretty > tiny, and it doesn't generally change. In particular since we > don't want to link gnutls into linux-user we shouldn't be requiring > the user to scrape up a static lib of it to keep things working. > Requiring gnutls at all for these configure options is just a bug > (in configure or the makefile).
Ok, I'll send a patch to auto-disable it when missing 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 :|
