From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LsBGF-0007y4-Rg for qemu-devel@nongnu.org; Fri, 10 Apr 2009 03:34:51 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LsBGF-0007xc-CI for qemu-devel@nongnu.org; Fri, 10 Apr 2009 03:34:51 -0400 Received: from [199.232.76.173] (port=52079 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LsBGF-0007xZ-6S for qemu-devel@nongnu.org; Fri, 10 Apr 2009 03:34:51 -0400 Received: from fg-out-1718.google.com ([72.14.220.157]:37867) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LsBGE-0008AX-4W for qemu-devel@nongnu.org; Fri, 10 Apr 2009 03:34:50 -0400 Received: by fg-out-1718.google.com with SMTP id l27so976506fgb.8 for ; Fri, 10 Apr 2009 00:34:49 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <20090410000758.GD29673@x40.openbsd.home.lan> References: <20090409164012.GA29673@x40.openbsd.home.lan> <20090410000758.GD29673@x40.openbsd.home.lan> Date: Fri, 10 Apr 2009 10:34:48 +0300 Message-ID: Subject: Re: [Qemu-devel] compilation issues of qemu, sparc64-bsd-user and OpenbSD From: Blue Swirl Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Mikolaj Kucharski , qemu-devel@nongnu.org On 4/10/09, Mikolaj Kucharski wrote: > On Thu, Apr 09, 2009 at 09:23:55PM +0300, Blue Swirl wrote: > > On 4/9/09, Mikolaj Kucharski wrote: > > > Hi, > > > > > > I'm trying to compile qemu-0.10.2 on OpenBSD 4.5 (pre-release) and I > > > have following issue with sparc64-bsd-user target. Everythine else > > > compiles, when I use --target-list and select all targets except > > > sparc64-bsd-user. > > > > > > Please see attached file for ./configure output. > > > > Does the attached patch help? I don't have an OpenBSD/i386 machine. > > > Yes, that fixed compilation problem. I would like to be notified > when your patch (or different fix for issue in this thread) get > commited to revision repository. Thank you. I've committed the patch to development branch as r7065, thanks for testing. This is not a bug fix, so I guess it doesn't qualify for the stable branch.