From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1G5LcH-0007tK-Tt for qemu-devel@nongnu.org; Tue, 25 Jul 2006 08:02:26 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1G5LcE-0007pR-K6 for qemu-devel@nongnu.org; Tue, 25 Jul 2006 08:02:24 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1G5LcE-0007p1-9r for qemu-devel@nongnu.org; Tue, 25 Jul 2006 08:02:22 -0400 Received: from [64.233.166.181] (helo=py-out-1112.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1G5LdX-0000bG-3e for qemu-devel@nongnu.org; Tue, 25 Jul 2006 08:03:43 -0400 Received: by py-out-1112.google.com with SMTP id d42so2659657pyd for ; Tue, 25 Jul 2006 05:02:21 -0700 (PDT) Message-ID: Date: Tue, 25 Jul 2006 05:02:21 -0700 From: "Jonathan Kalbfeld" Subject: Re: [Qemu-devel] Compile errors on Solaris for qemu 0.8.2 In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <44C4CD1E.1020706@win4lin.com> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Blue Swirl Cc: qemu-devel@nongnu.org I went ahead and made Leo's change and it built. Also, I bit the bullet and used the blastwave compiler. However, I still get segfaults trying to run sparc-test on qemu-system-sparc from my sparc/solaris box. Is this a known issue? Also happens with mips. On 7/24/06, Blue Swirl wrote: > >I ran into this myself yesterday. I couldn't figure out a definitive > >answer, because I am no expert on the SPARC architecture, but it appears > >that at least on an UltraSparc IIi machine from a few years ago, the > >"sparc V9" instructions are supported. However, the gcc by default > >doesn't define __sparc_v9__ on that architecture. There are some -m > >flags that can be passed to gcc (like multisparc, etc.), but I'm not > >sure for what host machines they are appropriate exactly. Perhaps the > >SPARC experts on the list can comment more, but in the meantime, the > >following simple (but likely incorrect) patch worked fine for me: > > Well, at least my gcc defines __sparc_v9__ if cpu is either v9, ultrasparc > or ultrasparc3: > %{mcpu=v9:-D__sparc_v9__} %{mcpu=ultrasparc:-D__sparc_v9__} > %{mcpu=ultrasparc3:-D__sparc_v9__} > > This is from /usr/lib/gcc-lib/sparc-linux/3.3.5/specs. What does your > compiler define, as you still can compile the RDTICK instruction in the > #ifdef section? RDTICK is not available on V8 (Sparc32) architecture, only > on V9. > > _________________________________________________________________ > FREE pop-up blocking with the new MSN Toolbar - get it now! > http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ > > -- -- Jonathan Kalbfeld +1 323 620 6682