Re: My work on cross compiler packages
On 2010年07月27日 13:06, Marcin Juszkiewicz wrote:
I started with reviewing gcc-4.4/4.5 and binutils packaging rules and merged
them as much as possible to get rid of *-cross.mk files which went bitrot a
bit. As result we got packages with debug versions of libraries, dependencies
are proper and as a bonus we got libmudflap cross compiled in case someone
binutils is harmless. In fact, I already have a very short shell script
that generates a source package for a targetted binutils package.
For gcc and libc, this is obviously a bit harder because bootstrapping
them requires both source trees and lots of jumping back and forth
between them, because libgcc and libc have a circular dependency on most
I'm currently re-bootstrapping an older system here using gcc 4.5, and I
find the bootstrap code to be significantly less broken than the one in
4.4 (specifically, the "all-host" target doesn't fail anymore), so I
suggest you start with 4.5 and backport from there.
To make it possible I also have to alter contents of *-source binary packages
from binutils/eglibc/gcc/linux to have a possibility to reuse their packaging
rules in new $ARCH-cross-compiler package on which I will work in next weeks.
I think we should have a "policy" document there, to allow uClibc to
provide a drop-in replacement for eglibc.