Shinkan wrote: > to compile with given versions of glibc/binutils, to be sure that > some bins will run on my target system. > > 1) Is there any other way to do that without emerging a > cross-compiler on my host ?
You could do it for the toolchain, and use eselect to pick which one should be active. For libc, I don't think it's possible. > I fixed that by cross-emerging ncurses on /usr/$CTARGET, then > retrying to cross-emerge bash on my real target. > Is there any conf-based way of telling cross-emerge to look for its > libs in my real target and not on /usr/$CTARGET. No. If you want bash within the empty target directory, you also need all it's dependencies in there. > I want /usr/$CTARGET to just have the cross-compiler. I wants > cros-emerged suff to be somewhere else. I don't think that's how it works, but I'll be honest and say that I haven't used this method myself. I've only done "direct" cross compilation, without emerge. //Peter
