Re: Bug#649094: xapt: paths not fixed in libc.so in cross packages
2011/11/18 Vincent Danjean <email@example.com>:
> Ok. So I will try to build a mips cross-compiler from stable as I'm doing
> know, ie with old tools (I need a cross compiler for my students quickly).
Sounds sensible and recommended.
> I will also try the buildcross package in experimental as this is
> the future.
No, buildcross is not the future. Currently there is a Debian
multiarch transition and cross tools need to be updated to cope with
multiarch. The future would be getting them into proper Debian.
Marcin, as par of its Linaro job, has been contributing some packages
which currently build properly on armel and armhf but fail on any
other architectures (at least for me) with the bug you are reporting.
For Emdebian future, I personally would like to switch to sysroot
enabled toolchains, so you can easily cross compile your application
and link against the libraries found in a sysroot directory, that
could easily be created by tools like debootstrap or multistrap. This
way, you are not forced to link against your system libraries, as your
target device could be running libraries totally different than your
So, Debian future is multiarch enabled cross toolchains. And Emdebian
proposed future are sysroot enabled toolchains.
Then dpkg-cross, xapt, .. and other tools will be removed from Debian.
For Emdebian, I would also wonder if it would make sense to create and
Android toolchain and uClibc cross toolchain, but time is limited and
there is not a real incentive yet (at least to me) to get them up and
running, so any contributions are more than welcome.
Also note I try to keep more or less up to date this wiki page:
Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-.