From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D9DMc-0004HL-46 for qemu-devel@nongnu.org; Wed, 09 Mar 2005 21:25:26 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D9DMa-0004GF-6D for qemu-devel@nongnu.org; Wed, 09 Mar 2005 21:25:25 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D9DJG-0003Cu-Km for qemu-devel@nongnu.org; Wed, 09 Mar 2005 21:21:58 -0500 Received: from [163.1.243.250] (helo=exchng3.physics.ox.ac.uk) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D9CjO-00058j-Pq for qemu-devel@nongnu.org; Wed, 09 Mar 2005 20:44:54 -0500 Message-ID: <422FA690.40502@physics.ox.ac.uk> Date: Wed, 09 Mar 2005 19:44:48 -0600 From: Stefan Stonjek MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] SO_BSDCOMPAT in qemu's syscall.c Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu developers Hello, I just tried to compile qemu 0.6.1 on SuSE Linux 9.2. Since a standard "configure ; make ; make install" failed, I checked the reason. The problem was that line 580 of syscall.c refers to a preprocessor constant SO_BSDCOMPAT. This should normaly come from /usr/include/asm/socket.h. Even though Redhat has this constant defined as 14, SuSE 9.2 does not have it at all. In fact 14 is not defined at all. Since I do not know what the situation is with other Linux distribution and since qemu compiles without SO_BSDCOMPAT I would like to know whether I could make sense to avoid this line. Thanks Stefan -- ************* Stefan Stonjek ******** s.stonjek1@physics.ox.ac.uk ****** * Univ. of Oxford; Physics Dept.; Keble Road; Oxford; OX1 3RH; UK * ******** phone: +44-1865-283111 ********** fax: +44-1865-273418 ******** * FNAL; MS 318; P.O. Box 500; Batavia, IL 60510, USA * +1-630-840-3066 *