Date: Tue, 14 Aug 2012 20:44:41 -0600 From: Warner Losh <imp@bsdimp.com> To: Adrian Chadd <adrian@freebsd.org> Cc: freebsd-arm@freebsd.org Subject: Re: Building ARM ports (was Re: Globalscale Dreamplug and 8.3 RELEASE) Message-ID: <48664E9B-0BBB-4C78-B720-9920083E661A@bsdimp.com> In-Reply-To: <CAJ-Vmok-n_focw5x4nM1Go2c0xRoeU=xehDAtTgeM2%2BtZ94GjA@mail.gmail.com> References: <5008728C.5040100@jetcafe.org> <1343846511.1128.34.camel@revolution.hippie.lan> <501B0E04.5040901@jetcafe.org> <1343951251.1128.53.camel@revolution.hippie.lan> <502AEC99.70708@jetcafe.org> <CAJ-Vmok-n_focw5x4nM1Go2c0xRoeU=xehDAtTgeM2%2BtZ94GjA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 14, 2012, at 6:35 PM, Adrian Chadd wrote: > Guys/girls/etc, >=20 > OpenWRT manages it. They started from the ground up with having to = cross-build. >=20 > Just because the problem is hard to tackle doesn't mean we shouldn't = try. Agreed. I worry the qemu solution sounds simple, but really will be = harder. Prove me wrong :) > There's like a dozen half-done attempts at this. I realise you can't > address _all_ the ports at once, but surely starting with a small > subset and working outward is doable. >=20 > I'll put up a bounty for anyone who actually comes up with a basic > framework for supporting cross-building ports, documents how it > does/doesn't work (eg if things like build vs run dependencies) and > has a basic design for how to slowly fix ports to support it. I have the basics, and have for years. I've posted them several times. = The trouble is that they are very very basic and need more work. I = think you'll need to define the problem a little better before progress = can be made. Warners
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?48664E9B-0BBB-4C78-B720-9920083E661A>