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