Cross-compiling done wrong

[MustrumR]

I'm talking about crossdev.

Why would glibc also be copied to cross-$CHOST/glibc? It would be far more correct if cross glibc was emerged with ROOT=/usr/$CHOST. I'm going to install stuff inside that root and glibc is a part of @system. I LOVE file collisions.

Also it would be easier if gcc, libgcc, libsupc++, libstdc++ and friends were also separate packages, like with clang/compiler-rt/libc++abi/libc++. I want to have libstdc++ on my router but I don't want gcc.

THIS IS MADNESS

[hasufell]

Yes, crossdev is misdesigned and even clashes with multilib depending on your use case (or just breaks compiling packages due to pkg-config being picked up wrong).

So... watch out.

[szatox]

I particularly second the point on making libstdc++ separate package. Some programs deppend on it even though they have nothing to do with programming themselves.