+++ Matthias Klose [2013-08-21 22:31 +0200]:
> Today the debian-cr...@lists.debian.org ML was created.
> Please subscribe to this list if you are interested in cross build issues.
Here: https://lists.debian.org/debian-cross/
Wookey
--
Principal hats: Linaro, Emdebian, Wookware, Balloo
+++ Wookey [2013-02-27 02:10 +]:
> State of the Debian/Ubuntu arm64 port
> =
>
> *** Arm64 lives! ***
>
> Executive summary
> -
>
> * There is now a bootable (raring) image to download and run
> * A bit m
+++ Ian Campbell [2013-02-27 12:00 +]:
> On Wed, 2013-02-27 at 02:10 +0000, Wookey wrote:
> >
> > Setting up an arm64 build environment is very simple. Use
> > sbuild-createchroot or mk-sbuild
> > and point at the bootstrap repo, with a bit of config and some updat
--host arm64 '.
The current bootstrap packageset status is here:
http://people.linaro.org/~wookey/buildd/raring-arm64/status-bootstrap.html
There is no armv8 (arm64/aarch64) hardware available yet, so this image can
currently only
be run in a model. ARM provide a free-beer prorietary 'Foun
4' and get a working cross-build environment.
The repo is here:
http://people.debian.org/~wookey/bootstrap.html
That should be useable for both dpkg-cross style bulding or
multiarch-style bulding.
The repo also contains updated dpkg-cross, multiarch python, multiarch
perl, updated dpkg wi
installable):
http://edos.debian.net/weather/weather.php?distro=testing&arch=armhf
(Is anyone running edos-distcheck on Ubuntu?)
The ongoing 'make multiarch cross-building work' process is also still
running and there are still easy pickings:
Logfiles:
http://people.linaro.org/~wookey/
-dependency/cross-building issues summarised here:
https://wiki.linaro.org/Platform/DevPlatform/CrossCompile/MultiarchCrossBuildStatus
with logfiles here
http://people.linaro.org/~wookey/buildd/precise/sbuild-ma/status.html
There is a pile of stuff, much of which is _really easy_. This page
tells
o think of potential use-cases, and I think ultimately,
unless the LSB is in fact entirely irrelevant, this work will get done
everntually. But should we get on with that now, rather than whatever
else we might be fixing, and if so, who is volunteering to get
involved?
( Jon Masters and I have bot
