qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* [Qemu-devel] buildbot failure in qemu on default_i386_macosx
@ 2012-11-02  4:01 qemu
  2012-11-02  7:17 ` Stefan Hajnoczi
  0 siblings, 1 reply; 4+ messages in thread
From: qemu @ 2012-11-02  4:01 UTC (permalink / raw)
  To: agraf, gollub, lcapitulino, qemu-devel

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


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Qemu-devel] buildbot failure in qemu on default_i386_macosx
  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
  0 siblings, 1 reply; 4+ messages in thread
From: Stefan Hajnoczi @ 2012-11-02  7:17 UTC (permalink / raw)
  To: Corey Bryant; +Cc: qemu-devel, Daniel Gollub, Alexander Graf, Luiz Capitulino

Corey, any ideas here?

  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
>

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [Qemu-devel] buildbot failure in qemu on default_i386_macosx
  2012-11-02  7:17 ` Stefan Hajnoczi
@ 2012-11-02 13:42   ` Corey Bryant
  0 siblings, 0 replies; 4+ messages in thread
From: Corey Bryant @ 2012-11-02 13:42 UTC (permalink / raw)
  To: Stefan Hajnoczi
  Cc: qemu-devel, Daniel Gollub, Alexander Graf, Luiz Capitulino



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
>>
>

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Qemu-devel] buildbot failure in qemu on default_i386_macosx
@ 2012-11-27  4:20 qemu
  0 siblings, 0 replies; 4+ messages in thread
From: qemu @ 2012-11-27  4:20 UTC (permalink / raw)
  To: agraf, gollub, lcapitulino, qemu-devel

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/27

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 git

sincerely,
 -The Buildbot


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2012-11-27  4:20 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
  -- strict thread matches above, loose matches on Subject: below --
2012-11-27  4:20 qemu

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).