Date: Wed, 28 Feb 2007 00:20:37 -1000 From: David Cornejo <dave@dogwood.com> To: "M. Warner Losh" <imp@bsdimp.com> Cc: freebsd-arm@freebsd.org Subject: Re: building ports for ARM Message-ID: <45e5577d.5a052323.3f11.ffffad26@mx.google.com> In-Reply-To: <20070228.030516.-432837530.imp@bsdimp.com> References: <45e53301.5e2ca738.28ab.2d6c@mx.google.com> <20070228.030516.-432837530.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
was afraid of this, with one of the netgate avila boards, some ports are taking days to compile due to swapping. barring cross-compiling, does anyone have a binary package repository, or might be interested in one? dave c At 12:05 AM 2/28/2007, M. Warner Losh wrote: >In message: <45e53301.5e2ca738.28ab.2d6c@mx.google.com> > David Cornejo <dave@dogwood.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45e5577d.5a052323.3f11.ffffad26>