Hi, Martin Michlmayr schrieb:
> BTW, it seems most of this stuff is not needed anymore. the GCC > package in Debian can easily build a cross-compiler now thanks to the > work by some Emdebian bloke. The same needs to be done for binutils. I think the most important aspect of that is the gcc-4.1-source package, as with that you can create a small package that just contains the necessary scripting to fully bootstrap a cross compiler. So far, toolchain-source both provided the source and the scripting, in order to really get the same functionality, we'd need to merge the "build scripting from template" stuff into the gcc package as well. In general I would agree that merging is good. One of my packages requires a compiler for i386-linux to build, another is going to require a compiler for arm-linux, it would be good if there were a way to do this sanely (for various levels of sanely, I'm currently thinking about Build-Depends-Indep: gcc-i386-cross | gcc-source [!i386], binutils-i386-cross | binutils-source [!i386] and simply building the necessary cross compiler from debian/rules) > Have you looked at how GCC does it now? It's really trivial. Bootstrapping is nontrivial these days, because someone fscked up the gcc build, so it no longer suffices to call the "all-host" rule to get a freestanding compiler you could use for kernel and libc, and then return to the gcc tree and invoke the "all" rule. Instead, you now need to configure gcc as freestanding, no shared libs, and compile your kernel and libc with that, then throw away your compiler and start anew. What would be needed is a way to build a freestanding compiler, then later on add libcs to the existing package, probably by editing the specs file. Simon (reprioritizing his todo list again)
signature.asc
Description: OpenPGP digital signature
