From: Sean Bruno <sbruno@ignoranthack.me>
To: sbruno@freebsd.org
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] bsd-user: master is broken
Date: Sun, 15 Jun 2014 13:06:41 -0700 [thread overview]
Message-ID: <1402862801.2347.10.camel@bruno> (raw)
In-Reply-To: <1402859429.2347.7.camel@bruno>
On Sun, 2014-06-15 at 12:10 -0700, Sean Bruno wrote:
> Trying to bisect a compile failure on master before I do anything else
> today. I'm getting a slew of linking failures right now due to
> unresolved symbols that appear to be needed by block/curl code.
>
> http://people.freebsd.org/~sbruno/ssl_fail_qemu.txt
>
> Lots of Curl_* functions and lots of SSL/Crypt functions here.
>
> Disabling curl support allows me to continue. (--disable-curl)
>
> This has happened in the last few days on master.
>
> sean
>
>
Looks like this is the culprit for me:
commit c5cb1afc4675bf5ff66e7a149d2a8cffba2eaa9e
Merge: b780bf8 1c33ac5
Author: Peter Maydell <peter.maydell@linaro.org>
Date: Wed Jun 11 15:36:48 2014 +0100
Merge remote-tracking branch 'remotes/bonzini/configure' into
staging
* remotes/bonzini/configure:
rules.mak: Rewrite unnest-vars
configure: unset interfering variables
configure: duplicate/incorrect order of -lrt
libcacard: improve documentation
libcacard: actually use symbols file
libcacard: replace qemu thread primitives with glib ones
vscclient: use glib thread primitives not qemu
glib-compat.h: add new thread API emulation on top of pre-2.31 API
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
next prev parent reply other threads:[~2014-06-15 20:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-15 19:10 [Qemu-devel] bsd-user: master is broken Sean Bruno
2014-06-15 20:06 ` Sean Bruno [this message]
2014-06-15 20:12 ` Sean Bruno
2014-06-15 20:48 ` Sean Bruno
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=1402862801.2347.10.camel@bruno \
--to=sbruno@ignoranthack.me \
--cc=qemu-devel@nongnu.org \
--cc=sbruno@freebsd.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).