From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1H9O7W-0007Mu-VI for qemu-devel@nongnu.org; Tue, 23 Jan 2007 11:03:38 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1H9O7U-0007IB-Uk for qemu-devel@nongnu.org; Tue, 23 Jan 2007 11:03:38 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1H9O7U-0007Hv-Oq for qemu-devel@nongnu.org; Tue, 23 Jan 2007 11:03:36 -0500 Received: from [64.233.182.188] (helo=nf-out-0910.google.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1H9O7T-0007Lz-NO for qemu-devel@nongnu.org; Tue, 23 Jan 2007 11:03:36 -0500 Received: by nf-out-0910.google.com with SMTP id c31so558639nfb for ; Tue, 23 Jan 2007 08:03:34 -0800 (PST) Message-ID: Date: Tue, 23 Jan 2007 17:03:31 +0100 From: VMiklos MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Subject: [Qemu-devel] [PATCH] fix i386-softmmu with newer kernel headers Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org hi with newer kernel-headers, i get the following compile error: gcc-3.3 -Wall -O2 -g -fno-strict-aliasing -fomit-frame-pointer -I. -I.. -I/var/tmp/fst/src/qemu-0.8.2/target-i386 -I/var/tmp/fst/src/qemu-0.8.2 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -I/var/tmp/fst/src/qemu-0.8.2/fpu -DHAS_AUDIO -I/var/tmp/fst/src/qemu-0.8.2/slirp -c -o usb-linux.o /var/tmp/fst/src/qemu-0.8.2/usb-linux.c /var/tmp/fst/src/qemu-0.8.2/usb-linux.c:29:28: linux/compiler.h: No such file or directory make[1]: *** [usb-linux.o] Error 1 make[1]: Leaving directory `/var/tmp/fst/src/qemu-0.8.2/i386-softmmu' make: *** [subdir-i386-softmmu] Error 2 is this a known issue? a trivial patch is here: http://darcs.frugalware.org/repos/frugalware-current/source/xapps-extra/qemu/qemu-0.8.2-include.diff i'm not sure about what would require that inclusion. i mean in case i would know, of course i would send some #ifndef FOO #include #endif patch :) thanks, VMiklos -- Developer of Frugalware Linux, to make things frugal - http://frugalware.org