On Wed, 01 Jun 2011 10:45:15 +0200 Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org> wrote: > On śro, 2011-06-01 at 09:34 +0100, Neil Williams wrote: > > Right now, nobody cares about cross-compilers in unstable because we > > don't have time to waste. > > What about cross-toolchain project at alioth? I am working on getting my > Ubuntu cross toolchains working in Debian: > > http://anonscm.debian.org/gitweb/?p=collab-maint/cross-toolchain.git;a=summary > > They build, they work. Status is on wiki page: > > https://wiki.linaro.org/MarcinJuszkiewicz/Projects/MergeCrossToolchainIntoDebian > > I do not provide packages for Debian but if someone wants I can share > results of my recent builds. The same problems as toolchains for unstable from Emdebian - the packages don't install because the dependencies keep on moving ahead without waiting for the cross-toolchain packages to be built and there is no sane way of upgrading a mixed range of -cross packages on an unstable base. Instead of doing yet another out-of-Debian toolchain build we really need to get one definitive set of cross-compiler toolchains into Debian using the Debian infrastructure and subject to all the normal Debian Policy requirements of migrations, RC bugs etc. The Emdebian toolchains for unstable can be installed with a fair bit of hacking around with the -armel-cross packages. The problem is that this is a permanent hassle which keeps on causing the toolchain to be removed by other Debian packaging upgrades in unstable. Maintaining a set of installable -cross packages against unstable is a pointless waste of time. Been there, got a couple of T-shirts, not doing that again. Use the toolchains from stable, put them into a disposable chroot like pbuilder (using, e.g. pdebuild-cross) and only install the -cross packages which are needed for one specific build, before throwing away the entire chroot and starting again from a pristine tarball. It's the only sane way of using cross-compiling toolchains currently, especially if the build-dependency chain of your package includes any "higher level" packages like libgtk2.0-dev or libqt4-dev. -- Neil Williams ============= http://www.linux.codehelp.co.uk/
Attachment:
pgpTwvz9x4TPf.pgp
Description: PGP signature