From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56017) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VKGla-0006SF-19 for qemu-devel@nongnu.org; Thu, 12 Sep 2013 19:57:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VKGlY-0003KT-SQ for qemu-devel@nongnu.org; Thu, 12 Sep 2013 19:57:41 -0400 Received: from speedy.comstyle.com ([2001:470:1d:8c::2]:36098 helo=mail.comstyle.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VKGlY-0003Fk-NK for qemu-devel@nongnu.org; Thu, 12 Sep 2013 19:57:40 -0400 Message-ID: <5232547F.3040706@comstyle.com> Date: Thu, 12 Sep 2013 19:55:43 -0400 From: Brad Smith MIME-Version: 1.0 References: <521F1AF0.5070400@ctshepherd.com> In-Reply-To: <521F1AF0.5070400@ctshepherd.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Buildbot Failures List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Charlie Shepherd Cc: anthony.perard@citrix.com, Stefan Hajnoczi , qemu-devel@nongnu.org, Alex Bligh , kraxel@redhat.com On 29/08/13 5:57 AM, Charlie Shepherd wrote: > Hi all, > > This is an attempt to do some triaging of the 18 current buildbot > failures[1]. > > default_openbsd_current (offline): > http://buildbot.b1-systems.de/qemu/builders/default_openbsd_current/builds/509/steps/compile/logs/stdio > > >> AS optionrom/multiboot.o >> Building optionrom/multiboot.img >> ld: multiboot.o: relocation R_X86_64_16 can not be used when making a >> shared object; recompile with -fPIC >> multiboot.o: could not read symbols: Bad value >> gmake[1]: *** [multiboot.img] Error 1 >> gmake: *** [romsubdir-optionrom] Error 2 > > This has been offline for a few weeks, I wonder if this issue has been > fixed in master since? I have been meaning to try and come up with a fix for this issue for awhile now. This has come about because OpenBSD 5.3 and newer now utilizes PIE by default on most of our architectures and building the ROM images needs to have PIE disabled. We have a patch in our ports tree to deal with this but it is not appropriate for upstream as is. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.