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.

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.

Best regards,
Michał Górny

Attachment: pgpxIrlqF6nnb.pgp
Description: OpenPGP digital signature

Reply via email to