+++ Wookey [2012-06-27 20:04 +0100]:
> +++ Wookey [2012-01-19 14:32 +0000]:
> > +++ Neil Williams [2012-01-19 13:02 +0000]:
> > > On Thu, 19 Jan 2012 12:10:28 +0000
> > > Wookey <email@example.com> wrote:
> > >
> > > > I've thought for a long time that a package like build-essential for
> > > > cross-building would be a really good idea.
> > >
> > > +1
> > >
> > > It should probably depend on build-essential itself as a starting point.
> > I suppose so. You won't get far without that.
> OK, there has been progress in this area. Thanks to Patrick McDermmot
> (GSOC student) we have a patch to add support to build-essential for a
> crossbuild-essential-<arch> packages.
I've now munged this a fair amount to actually work, and tested it on
the arm64 bootstrap as well as some armel and armhf builds. It all
works rather nicely.
I've filed a bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693220
to try and reach a conclusion on the matter of having one source
pakcage that produce the build-essential and
crossbuild-essential-<arch> packages. Or having this done as a
separate source package.
It was designed to be merged, but the version in the repo has the
native bits commented out so is effectively a separate (but rather
similar) source package:
(the testing has been done in Ubuntu as the toolchains are already
in-archive, so it would need a few package-name changes for Debian,
which I expect to get to soon - that makes no difference to the
Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM