|Deletions are marked like this.||Additions are marked like this.|
|Line 21:||Line 21:|
|=== What changes do I have to do to the linux-kernel-headers source package so I can
build them for a uclibc-* architecture? ===
|=== What changes do I have to do to the linux-kernel-headers source package so I can build them for a uclibc-* architecture? ===
Frequently Asked Questions
Where do I download the Emdebian distribution?
The project is still working on tools, mechanisms and infrastructure to build a distro, but we do now have a couple of minimal working distributions you can try.
EmdebianSlind is a pure dpkg-cross based system, where the built filesystem is NFS-mounted on the target to complete installation.
The other is a distro which uses scratchbox for the cross-building: [http://stage.maemo.org/pool/ Ed Bartosh's work]. Emdebian is in the process of deciding which of these approaches to use, or combining their good bits if possible.
what do I need to build a uclibc toolchain in debian?
http://www.emdebian.org/docs/slind-toolchain.html You need to patch your binutils http://www.emdebian.org/slind/patches/binutils-slind.diff and you need slinds version of dpkg-cross. slind dpkg-dev isn't absolutely necessary. you can change /usr/share/dpkg/ files instead to support uclibc. Also you need to use the uclibc source from slind. gcc is just fine. (I don't know if all this is correct, I'll fix this later together with detailed instructions for dpkg-dev)
...and a glibc toolchain?
Just follow the same instructions as in http://www.emdebian.org/docs/slind-toolchain.html - but use normal debian sources. at least in Sid that should work.
What changes do I have to do to the linux-kernel-headers source package so I can build them for a uclibc-* architecture?
sorry, all this doesn't work,yet. all of it should work with the next version of lkh, though. when bootstrapping in the phase where you have no target compiler you have to disable the tests: setting DEB_BUILD_OPTIONS=nocheck will do that. uclibc support should be in it very soon now.
Should I build my own cross toolchain - or use a prebuilt one?
That depends on what you want to do. If you want to build for a eisting set of applications and libraries it is a good idea to use the toolchain they used. If you are starting from scratch you can build your own. it's not that hard. the toolchain howto on the emdebian site helps. also have a look at the README.cross in binutils and gccs debian dir.