From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:58335) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TGSsS-0004sA-Bj for qemu-devel@nongnu.org; Tue, 25 Sep 2012 07:00:33 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TGSsM-0006OL-CF for qemu-devel@nongnu.org; Tue, 25 Sep 2012 07:00:32 -0400 Received: from mx1.redhat.com ([209.132.183.28]:18447) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TGSsM-0006NV-3v for qemu-devel@nongnu.org; Tue, 25 Sep 2012 07:00:26 -0400 Message-ID: <50618EBF.2050207@redhat.com> Date: Tue, 25 Sep 2012 13:00:15 +0200 From: Gerd Hoffmann MIME-Version: 1.0 References: <50616F9E.5000501@redhat.com> <5061896D.4020107@redhat.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [RfC] using pixman in qemu for raster ops List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: "qemu-devel@nongnu.org" , Stefano Stabellini On 09/25/12 12:48, Peter Maydell wrote: > On 25 September 2012 11:37, Gerd Hoffmann wrote: >> On 09/25/12 11:31, Peter Maydell wrote: >>> For me "not a standard library package on RHEL5" is a strong argument >>> against adding a hard dependency. (For instance, most of the compute >>> cluster machines here are RHEL5 and it would be pretty awkward to >>> deal with manually building a dependent library.) >> >> Why it is that a big deal? Whatever is used to distribute qemu to the >> cluster machines (local yum repo?) can be used to distribute pixman too, no? > > There's a big leap between "run configure, put the qemu executable > in some generally available directory" and "you have to first get > and build some third party library, install it somewhere, tell > configure where you put it, then build qemu, then make sure that > not just the qemu executable but also this third party library > are on all the machines". At the moment you can build qemu without > any non-system dependencies, and we should have a really good > reason for breaking that. Hmm, we could import a pixman copy into the qemu tree and use that as fallback if we don't find pixman installed on the system ... cheers, Gerd