Re: Bug#693220: Add crossbuild-essential support
On Wed, Nov 14, 2012 at 12:08:26PM +0000, Wookey wrote:
> Following on from discussion in this thread
> The cross-build-essential package has been developed some more and
> tested in Quantal for arm64 bootstrap, and armel and armhf builds. It
> works nicely. We definitely want to start using this.
> The latest code is available at:
I think it would be a good idea to put this in build-essential, but I
have one concern. At the moment this uses "Depends: libc6-dev:armhf"
(etc.). The multiarch spec currently explicitly says that Depends on
PKG:ARCH for a particular architecture (as opposed to PKG:any) is
undefined. I'm therefore a bit worried that adding such syntax to
build-essential would cause some bit of archive machinery to explode; it
certainly results in a Lintian error. That said, it apparently works in
simple sbuild chroot situations. CCing -embedded and -dpkg for advice.
The other possibility is to add bridging dependencies by way of
artificial package names that only exist on one architecture, e.g.:
That's not without its own problems, though; it bloats Packages and
(last I checked) it requires manually forcing britney to accept it into
testing. If it's possible to use the :ARCH syntax instead, that would
Colin Watson [email@example.com]