| 1 |
I'm using the xmerge idea that was posted online, but I've noticed |
| 2 |
something I found quite odd: |
| 3 |
|
| 4 |
after emerging a toolchain w/ crossdev, and then using xmerge to build / |
| 5 |
install packages, I noticed that $SYSROOT/lib and $SYSROOT/usr/lib were |
| 6 |
linked to /usr/<toolchain>/lib and /usr/<toolchain>/usr/lib, respectively. |
| 7 |
|
| 8 |
ls -la $SYSROOT/ $SYSROOT/usr/ | grep "lib" |
| 9 |
|
| 10 |
lib -> ../usr/arm-9tdmi-linux-gnu/lib |
| 11 |
lib -> ../../usr/arm-9tdmi-linux-gnu/usr/lib |
| 12 |
|
| 13 |
It affects me quite badly in particular because I have been working on a |
| 14 |
build system that is intended to support multiple target architectures, |
| 15 |
multiple configurations for each target, as well as multiple profiles |
| 16 |
for each configuration. (configurations could be client-specific, and |
| 17 |
profiles are 'package.{use,keyword}' variant, for instance 'stable', |
| 18 |
'devel'). |
| 19 |
|
| 20 |
Does anyone know why the libraries are set up in this manner, and not |
| 21 |
just copied as one would expect to legitimate directories? I appreciate |
| 22 |
that it makes cross-compilation much easier, however, wouldn't the |
| 23 |
proper handling of it be to actually copy the files to their intended |
| 24 |
directories (maybe add another -L / -I option in to <arch>-gcc commands?) |
| 25 |
|
| 26 |
How would I go about fixing this? Is this something deeply engrained in |
| 27 |
Portage? |
| 28 |
|
| 29 |
~/Chris |
| 30 |
|
| 31 |
-- |
| 32 |
gentoo-embedded@g.o mailing list |
Archives