From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IEVyO-0000QF-CK for qemu-devel@nongnu.org; Fri, 27 Jul 2007 15:59:40 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IEVyM-0000PY-R3 for qemu-devel@nongnu.org; Fri, 27 Jul 2007 15:59:40 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IEVyM-0000PT-Ml for qemu-devel@nongnu.org; Fri, 27 Jul 2007 15:59:38 -0400 Received: from ug-out-1314.google.com ([66.249.92.168]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1IEVyM-0003fg-85 for qemu-devel@nongnu.org; Fri, 27 Jul 2007 15:59:38 -0400 Received: by ug-out-1314.google.com with SMTP id m2so726355uge for ; Fri, 27 Jul 2007 12:59:37 -0700 (PDT) Message-ID: <46AA4DA4.2030900@gmail.com> Date: Fri, 27 Jul 2007 21:55:16 +0200 From: Sunil Amitkumar Janki MIME-Version: 1.0 Subject: Re: QEMU Automated Testing (was [Qemu-devel] qemu Makefile.target vl.h hw/acpi.c hw/adlib.c ...) References: <1175990048.1516.77.camel@rapid> <20070408000420.GJ21953@networkno.de> <1176018595.1516.115.camel@rapid> <20070408144103.GM21953@networkno.de> <1176049887.1516.209.camel@rapid> <000c01c77a1e$8bc6d620$a3548260$@com> <20070727142142.GX8527@erizo.shearer.org> <46AA0137.8060007@codemonkey.ws> <20070727143404.GA16020@erizo.shearer.org> <46AA080B.9040902@gmail.com> <20070727185154.GE26960@networkno.de> In-Reply-To: <20070727185154.GE26960@networkno.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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: , Cc: qemu-devel@nongnu.org Thiemo Seufer wrote: > A missing libm sounds like a build environment problem. > > Thiemo Do you have a test for this because I reinstalled the entire system from scratch and have had no problems building lots of packages over the last week except for those applications that assume that all the world is an x86? The only thing I have had to do is getting a GCC 3.4.6 compiler setup which I did by configuring and packaging it to "/opt/gcc/3.4.6" and including it in the path and making it the default using a script in "/usr/bin" and reversing that again. I *do* have it configured with "--with-arch=r4600", which may have led to problems. It's really painful for me to go back to some hacked up previous os release, that was not done by me, on which I can rebuild GCC 3.4.6 without this option, but I will if I really have to. It works well for several packages that don't compile with GCC 4.1.2, which is the system compiler and seems to be the accepted default nowadays in all distributions. I guess the best solution would be to change QEMU to make it build with GCC4 but I understand that may not be an easy endeavour to undertake because of fundamental design issues. Sunil