| 1 |
On Tuesday 26 September 2006 12:24, Daniel Glaser wrote: |
| 2 |
> OK, to better understand this... |
| 3 |
> Does this mean, if you make your Target-ROOT /usr/CTARGET, the two |
| 4 |
> locations ($ROOT and /usr/CTARGET) mentioned above goes into the same |
| 5 |
> place, so that gcc, ld,... can find it? |
| 6 |
|
| 7 |
your cross-compiler uses /usr/CTARGET as the sysroot ... in other words, it's |
| 8 |
as if /usr/CTARGET were the $ROOT for just the compiler |
| 9 |
|
| 10 |
binutils and gcc treat /usr/CTARGET/lib and /usr/CTARGET/usr/lib |
| 11 |
and /usr/CTARGET/usr/include the same exact way your native compiler |
| 12 |
treats /lib and /usr/lib and /usr/include |
| 13 |
|
| 14 |
so lets look at nano ... it needs ncurses |
| 15 |
|
| 16 |
ROOT=/usr/CTARGET emerge -b ncurses |
| 17 |
ROOT=/home/myboard emerge -K ncurses |
| 18 |
ROOT=/home/myboard emerge nano |
| 19 |
|
| 20 |
the only thing you need to set is CHOST ... no screwing with CFLAGS or LDFLAGS |
| 21 |
as the toolchain already knows where to look |
| 22 |
-mike |
Archives