В Tue, 9 Dec 2014 17:21:22 +0100
Michał Górny <mgo...@gentoo.org> пишет:

> Dnia 2014-12-08, o godz. 09:56:11
> Alexis Ballier <aball...@gentoo.org> napisał(a):
> 
> > On Sun, 7 Dec 2014 11:37:57 +0100
> > Michał Górny <mgo...@gentoo.org> wrote:
> > 
> > > 1. No cross-compilation support. If the project proves being a success
> > > it will be readded at some point. However, I will likely fork glibc
> > > first and work on a sane crossdev alternative.
> > 
> > Could you please elaborate on this ?
> > How and why this broke, what is wrong in glibc, what would be a "sane
> > crossdev alternative" and how crossdev is not.
> 
> 1. eblits are broken in glibc. Another case of incorrect interpretation
> of code sharing with love for breaking stable ebuilds. Plus I'd love to
> add multilib flags to it but we'll likely doing that to main glibc as
> well soon, if eblits don't get into our way.

Yeah. Stable glibc ebuild gets broken from time to time after changes
in eblits.

> 
> 2. crossdev is broken because it creates semi-random, unmaintained
> ebuilds in randomly chosen overlay, those ebuilds relying on
> toolchain.eclass behavior.
> 
> 3. I don't have any real alternative design yet. However, one 
> of the first ideas of changing crossdev is to replace copying ebuilds
> with symlinking gcc ebuild directory. This will at least ensure proper
> sync between real ebuilds and cross-ebuilds.
> 

crossdev already works that way for a long time (see -oO option in
help):

$ ls -l /var/cache/portage/repos/crossdev/cross-armv6j-hardfloat-linux-gnueabi/
total 0
lrwxrwxrwx 1 portage portage 42 Oct 23 22:24 binutils -> 
/var/cache/portage/tree/sys-devel/binutils
lrwxrwxrwx 1 portage portage 37 Oct 23 22:24 gcc -> 
/var/cache/portage/tree/sys-devel/gcc
lrwxrwxrwx 1 portage portage 37 Oct 23 22:24 gdb -> 
/var/cache/portage/tree/sys-devel/gdb
lrwxrwxrwx 1 portage portage 38 Oct 23 22:24 glibc -> 
/var/cache/portage/tree/sys-libs/glibc
lrwxrwxrwx 1 portage portage 48 Oct 23 22:24 linux-headers -> 
/var/cache/portage/tree/sys-kernel/linux-headers

-- 
Alexander Tsoy

Reply via email to