From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:39127) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TaLCC-00046f-5n for qemu-devel@nongnu.org; Mon, 19 Nov 2012 01:51:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TaLC9-0006Kn-2e for qemu-devel@nongnu.org; Mon, 19 Nov 2012 01:51:04 -0500 Received: from v220110690675601.yourvserver.net ([78.47.199.172]:41189) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TaLC8-0006KB-SZ for qemu-devel@nongnu.org; Mon, 19 Nov 2012 01:51:01 -0500 Message-ID: <50A9D6D1.9080900@weilnetz.de> Date: Mon, 19 Nov 2012 07:50:57 +0100 From: Stefan Weil MIME-Version: 1.0 References: <20121118234315.AEA8541A84@buildbot.b1-systems.de> In-Reply-To: <20121118234315.AEA8541A84@buildbot.b1-systems.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] buildbot failure in qemu on default_i386_debian_6_0 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: qemu-devel@nongnu.org, gollub@b1-systems.de, agraf@suse.de, lcapitulino@redhat.com Am 19.11.2012 00:43, schrieb qemu@buildbot.b1-systems.de: > The Buildbot has detected a new failure on builder default_i386_debian_6_0 while building qemu. > Full details are available at: > http://buildbot.b1-systems.de/qemu/builders/default_i386_debian_6_0/builds/454 > > Buildbot URL: http://buildbot.b1-systems.de/qemu/ > > Buildslave for this Build: yuzuki > > Build Reason: The Nightly scheduler named 'nightly_default' triggered this build > Build Source Stamp: [branch master] HEAD > Blamelist: > > BUILD FAILED: failed test > > sincerely, > -The Buildbot LINK tests/test-coroutine osdep.o: In function `qemu_close': osdep.c:(.text+0x4b1): undefined reference to `monitor_fdset_dup_fd_find' osdep.c:(.text+0x51b): undefined reference to `monitor_fdset_dup_fd_remove' At least some test executables need libqemustub.a. I also noted that QEMU tries to build several 32 bit applications for the tests even on 64 bit hosts. We currently don't check whether the host supports 32 bit builds. Here a check in configure should be added. On a Debian host, I had to install those packages: 2012-11-19 07:24:41 status installed libc6-i386 2.11.3-4 2012-11-19 07:24:41 status installed libc6-dev-i386 2.11.3-4 2012-11-19 07:30:22 status installed lib32gcc1 1:4.4.5-8 2012-11-19 07:30:22 status installed lib32gomp1 4.4.5-8 2012-11-19 07:30:22 status installed gcc-4.4-multilib 4.4.5-8 2012-11-19 07:30:22 status installed gcc-multilib 4:4.4.5-1 'make test' still fails because more 32 bit packages are missing: gcc -m32 -o test_path test_path.o -lrt -pthread -lgthread-2.0 -lrt -lglib-2.0 /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.4.5/../../../libgthread-2.0.so when searching for -lgthread-2.0 /usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.4.5/../../../libgthread-2.0.a when searching for -lgthread-2.0 /usr/bin/ld: skipping incompatible /usr/lib/libgthread-2.0.so when searching for -lgthread-2.0 /usr/bin/ld: skipping incompatible /usr/lib/libgthread-2.0.a when searching for -lgthread-2.0 /usr/bin/ld: cannot find -lgthread-2.0 collect2: ld returned 1 exit status make[1]: *** [test_path] Fehler 1 This needs a configure check, too (or 'make test' should skip that test if there is no 32 bit libgthread-2.0). Regards Stefan