From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LgNuS-0005Q1-43 for qemu-devel@nongnu.org; Sun, 08 Mar 2009 14:39:36 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LgNuQ-0005Pf-9X for qemu-devel@nongnu.org; Sun, 08 Mar 2009 14:39:35 -0400 Received: from [199.232.76.173] (port=48501 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LgNuQ-0005Pc-33 for qemu-devel@nongnu.org; Sun, 08 Mar 2009 14:39:34 -0400 Received: from smtp6-g21.free.fr ([212.27.42.6]:35004) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LgNuP-0007mz-9o for qemu-devel@nongnu.org; Sun, 08 Mar 2009 14:39:33 -0400 In-Reply-To: <49B40B5F.9070507@codemonkey.ws> Subject: Re: [HaikuPorts-devs] [Qemu-devel] Re: [PATCH] [RFC] Haiku host support and general configure issues From: "=?utf-8?q?Fran=C3=A7ois?= Revol" Date: Sun, 08 Mar 2009 19:41:28 +0100 CET Message-Id: <8416999557-BeMail@laptop> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: haikuports-devs@ports.haiku-files.org, qemu-devel@nongnu.org > >> Well we should have a pthread lib available though... > > > > It's part of libroot.so, I thought, and thus referenced without > > extra > > linker arguments. > > So we should try to compile against -lpthread and then try to compile > against -lroot. Or better yet, does -pthread do the right thing on > haiku=3F We could just switch to that. -lroot is implied, not needed, so pthread is available without any flag. > >> Another big issue that I mentionned earlier here is the widely > > > used > >> assumption that error codes are positive, which is not the case > > > for > >> BeOS and Haiku. > >> Not fixing this will result in a dangerous binary. > > > > Thanks for the reminder. But that also reminds me, you wanted to > > supply a patch for that! :) > > Such a patch may be something ya'll have to maintain on your own. > This > has been discussed a lot in the past and I'm concerned that it's > going > to be too invasive. Too busy to start on it again. There is nothing wrong with it if done cleanly. It might even help catch up mistakes. Fran=C3=A7ois.