On Mon, Aug 20, 2012 at 08:41:19AM +0200, Marcin Juszkiewicz wrote: > W dniu 19.08.2012 21:42, Thibaut Girka pisze: > > > I have given thought about how cross-compilers could be built > > automatically, but I haven't found out a good way to do that yet. It > > is impossible to build multiarch cross-toolchains as part of the > > normal build of gcc, since src:gcc-4.7 would then require > > libgcc1:$host and (libgcc1:$target for each $target in the targets > > list) to be of the same version. > > Also when cross build for arch X fails then whole package fails. Right. > > Another solution would be to have another source package, responsible > > for building cross-compilers from gcc's source package. As far as I > > know, that's how it is done for ubuntu, but apt-get sourcing gcc-4.7 > > from a source package feels wrong to me... > > I went that way with gcc-4.[4-7]-armel-cross in Ubuntu. Easy, simple, > some packages mangling required. Same way with binutils-armel-cross. So > please take a look at them. I took a look at them! Although I have to admit I only remember looking at the “armel-cross-toolchain-base” branch, which boostraps the whole thing. Now, I'm looking at the “gcc-4.x-cross” branch, and it is really close to what I had in mind. I would like to avoid the duplication in the control file and override files, though... I'll think about that, but it's post-GSoC, now ;) Regards, Thibaut Girka.
Attachment:
signature.asc
Description: Digital signature