From: Corey Bryant <coreyb@linux.vnet.ibm.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
Daniel Gollub <gollub@b1-systems.de>,
Alexander Graf <agraf@suse.de>,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] buildbot failure in qemu on default_i386_macosx
Date: Fri, 02 Nov 2012 09:42:21 -0400 [thread overview]
Message-ID: <5093CDBD.8060409@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAJSP0QVkJJW0iAaThiBAcD9zay_+knXVZPEPXizcm3ccakP10Q@mail.gmail.com>
On 11/02/2012 03:17 AM, Stefan Hajnoczi wrote:
> Corey, any ideas here?
>
My guess for the majority of these is that monitor.o is not being linked
with osdep.o for MacOSX. Is this a nightly build that would have been
successful earlier in the week? Also do you know if (and perhaps how) I
can cross compile on Fedora to recreate this?
--
Regards,
Corey Bryant
> LINK qemu-ga
> Undefined symbols:
> "_monitor_get_fd", referenced from:
> _socket_connect in qemu-sockets.o
> _socket_listen in qemu-sockets.o
> "_monitor_fdset_dup_fd_find", referenced from:
> _qemu_close in osdep.o
> "_sem_timedwait", referenced from:
> _qemu_sem_timedwait in qemu-thread-posix.o
> "_monitor_fdset_dup_fd_remove", referenced from:
> _qemu_close in osdep.o
> "_monitor_fdset_get_fd", referenced from:
> _qemu_open in osdep.o
> "_qemu_set_fd_handler2", referenced from:
> _inet_connect_addr in qemu-sockets.o
> _wait_for_connect in qemu-sockets.o
> _unix_connect_opts in qemu-sockets.o
> "_monitor_fdset_dup_fd_add", referenced from:
> _qemu_open in osdep.o
> ld: symbol(s) not found
>
> On Fri, Nov 2, 2012 at 5:01 AM, <qemu@buildbot.b1-systems.de> wrote:
>> The Buildbot has detected a new failure on builder default_i386_macosx while building qemu.
>> Full details are available at:
>> http://buildbot.b1-systems.de/qemu/builders/default_i386_macosx/builds/2
>>
>> Buildbot URL: http://buildbot.b1-systems.de/qemu/
>>
>> Buildslave for this Build: MacOSX-10.5
>>
>> Build Reason: The Nightly scheduler named 'nightly_default_5oclock' triggered this build
>> Build Source Stamp: [branch master] HEAD
>> Blamelist:
>>
>> BUILD FAILED: failed compile
>>
>> sincerely,
>> -The Buildbot
>>
>
next prev parent reply other threads:[~2012-11-02 13:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 4:01 [Qemu-devel] buildbot failure in qemu on default_i386_macosx qemu
2012-11-02 7:17 ` Stefan Hajnoczi
2012-11-02 13:42 ` Corey Bryant [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-11-27 4:20 qemu
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=5093CDBD.8060409@linux.vnet.ibm.com \
--to=coreyb@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=gollub@b1-systems.de \
--cc=lcapitulino@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
/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).