From owner-freebsd-security@FreeBSD.ORG  Wed Oct 26 05:24:23 2005
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
X-Original-To: freebsd-security@FreeBSD.org
Delivered-To: freebsd-security@FreeBSD.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 847DB16A420;
	Wed, 26 Oct 2005 05:24:23 +0000 (GMT) (envelope-from imp@bsdimp.com)
Received: from harmony.bsdimp.com (vc4-2-0-87.dsl.netrack.net [199.45.160.85])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1B9F443D46;
	Wed, 26 Oct 2005 05:24:23 +0000 (GMT) (envelope-from imp@bsdimp.com)
Received: from localhost (localhost.village.org [127.0.0.1] (may be forged))
	by harmony.bsdimp.com (8.13.3/8.13.3) with ESMTP id j9Q5NQUl017129;
	Tue, 25 Oct 2005 23:23:27 -0600 (MDT) (envelope-from imp@bsdimp.com)
Date: Tue, 25 Oct 2005 23:23:23 -0600 (MDT)
Message-Id: <20051025.232323.93475319.imp@bsdimp.com>
To: kris@obsecurity.org
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20051025170934.GA29561@xor.obsecurity.org>
References: <20051024080811.GF39882@cirb503493.alcatel.com.au>
	<20051025004757.GH14063@obiwan.tataz.chchile.org>
	<20051025170934.GA29561@xor.obsecurity.org>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0
	(harmony.bsdimp.com [127.0.0.1]);
	Tue, 25 Oct 2005 23:23:28 -0600 (MDT)
X-Mailman-Approved-At: Wed, 26 Oct 2005 17:14:45 +0000
Cc: jeremie@le-hen.org, developers@FreeBSD.org, PeterJeremy@optushome.com.au,
	obrien@FreeBSD.org, freebsd-security@FreeBSD.org, delphij@delphij.net
Subject: Re: Is it feasible to cross-build compat5x binary?
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Security issues \[members-only posting\]"
	<freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
	<mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
	<mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Oct 2005 05:24:23 -0000

In message: <20051025170934.GA29561@xor.obsecurity.org>
            Kris Kennaway <kris@obsecurity.org> writes:
: On Tue, Oct 25, 2005 at 02:47:57AM +0200, Jeremie Le Hen wrote:
: > Hi Peter and others,
: > 
: > > At some stage, we need to validate our cross-build chain with cmp(1).
: > > We can probably leverage off the work that NetBSD has done in this
: > > area.  This would significantly simplify the work involved in supporting
: > > the various architectures.
: > 
: > in case you know enough about NetBSD's build.sh, can you say if FreeBSD's
: > build architecture is powerful enough to merely use it with a few s///
: > or does it still lack one or more things ?
: 
: I expect it's pretty different.  ru@ did a lot of work on
: cross-building FreeBSD though, and he had a fairly detailed list
: of known differences between cross-built and native builds.  I'm not
: sure if he reduced it to 0 length.

NetBSD build.sh runs great on FreeBSD, when building NetBSD sources
that is :-).

I know that cross builds for i386 from amd64 work well enough.
However, we[*] was unable to get a full cross build for i386 world
seutp on my amd64 machine when last I tried.

Warner

[*] tried to setup a dual amd64 box as our build server for our
embedded FreeBSD/i386 product.  It was quite a bit more complicated
than just a normal cross build, but there were many issues that our
(both FreeBSD and our company's) build system paper over for a few
edge cases that seem to not matter...