From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1HJKR7-0008Ud-MG
	for qemu-devel@nongnu.org; Mon, 19 Feb 2007 21:08:57 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1HJKR5-0008So-ME
	for qemu-devel@nongnu.org; Mon, 19 Feb 2007 21:08:57 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1HJKR5-0008Sd-Gt
	for qemu-devel@nongnu.org; Mon, 19 Feb 2007 21:08:55 -0500
Received: from eastrmmtao04.cox.net ([68.230.240.35])
	by monty-python.gnu.org with esmtp (Exim 4.52) id 1HJKR5-0001n6-1v
	for qemu-devel@nongnu.org; Mon, 19 Feb 2007 21:08:55 -0500
Message-ID: <20894890.1171937332995.JavaMail.root@eastrmwml08.mgt.cox.net>
Date: Mon, 19 Feb 2007 21:08:52 -0500
From: Ben Taylor <sol10x86@cox.net>
Subject: Re: [Qemu-devel] FreeBSD Support
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Reply-To: sol10x86@cox.net, qemu-devel@nongnu.org
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: Christopher Olsen <cwolsen@domainatlantic.com>


---- Christopher Olsen <cwolsen@domainatlantic.com> wrote: 
> This is a sidetrack here... But is it at all possible to make future releases 
> of the source more FreeBSD friendly?
> 
> I am willing to work off a specified codebase to bring it up to FreeBSD speed 
> so it can be easily maintained from there... 
> 
> Because unfortunately out of the box it doesn't build.

Having been in your shoes, the only thing I can tell you is start
small.  Be able to justify your patches and change as little as
possible.  Be smart about how you code things if there are 
specific reasons.  And get ready for a long haul.  Be ready to
constantly be porting your changes through the CVS tree.

I can tell you that you won't be able to submit a 

"This patch makes it work with FreeBSD"

and have it accepted.

Start with the configure script and Makefiles, and any very specfic, targeted
and small patches  and let those changes slowly propogate out.

HTH,

Ben