From owner-freebsd-arm@FreeBSD.ORG Wed Feb 28 10:07:31 2007 Return-Path: X-Original-To: freebsd-arm@freebsd.org Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9CE1F16A402 for ; Wed, 28 Feb 2007 10:07:31 +0000 (UTC) (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 5EF9813C47E for ; Wed, 28 Feb 2007 10:07:31 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from localhost (localhost [127.0.0.1]) by harmony.bsdimp.com (8.13.4/8.13.4) with ESMTP id l1SA5D3m084455; Wed, 28 Feb 2007 03:05:14 -0700 (MST) (envelope-from imp@bsdimp.com) Date: Wed, 28 Feb 2007 03:05:16 -0700 (MST) Message-Id: <20070228.030516.-432837530.imp@bsdimp.com> To: dave@dogwood.com From: "M. Warner Losh" In-Reply-To: <45e53301.5e2ca738.28ab.2d6c@mx.google.com> References: <45e53301.5e2ca738.28ab.2d6c@mx.google.com> X-Mailer: Mew version 4.2 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]); Wed, 28 Feb 2007 03:05:14 -0700 (MST) Cc: freebsd-arm@freebsd.org Subject: Re: building ports for ARM X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Feb 2007 10:07:31 -0000 In message: <45e53301.5e2ca738.28ab.2d6c@mx.google.com> David Cornejo writes: : Is there some generic way to cross-compile ports for the ARM? Some : ports seem to be ok by overriding the CC/LD/etc. definitions, but : others attempt to build stuff using compiled binaries... No. There's some things that can be done to make this process easier. However, there are four kinds of ports: simple, host tools needed and no cross support, with broken cross support, with working cross support. Only the first and the last can work. The last works by telling config to use its cross config to build. The first works by telling it to use ALL tools for cross build. I have a bunch of patches to install the cross tools into /usr/arm-freebsd so that autoconfig for the working ports can work, and a string of CC=, LD=, etc can work for the simple ports. I've not had time to integrate those into the tree yet. I also have some half-assed patches to ports as of about 4.8 that can help a little, but that don't apply cleanly to present ports... Warner