| 1 |
I installed the following toolchain with crossdev: |
| 2 |
arm-unknown-linux-gnueabi |
| 3 |
which installs glibc into /usr/arm-unknown-linux-gnueabi/ under the |
| 4 |
name cross-arm-unknown-linux-gnueabi/glibc |
| 5 |
|
| 6 |
I then installed udev, which depends on sys-fs/glibc |
| 7 |
|
| 8 |
As far as I know sys-fs/glibc is already installed into SYSROOT, except |
| 9 |
with a different name as mentioned above. |
| 10 |
|
| 11 |
I noted that the two installs of glibc had the same version, so I went |
| 12 |
ahead with the installation anyway. Sure enough portage reported a bunch |
| 13 |
of file collisions. |
| 14 |
|
| 15 |
I'm guessing that the solution is to move SYSROOT into another |
| 16 |
directory. I think I've seen how to do this in some documentation, but I |
| 17 |
can't find it anymore. Would setting SYSROOT to another directory |
| 18 |
separate the two glibc installs? I was also wondering if it was possible |
| 19 |
to ask portage to install packages and build filesystem in directories |
| 20 |
owned by users. The advantage of which is to let users create their own |
| 21 |
filesystems in more a of a sandbox environment. |
| 22 |
|
| 23 |
Thanks, |
| 24 |
Chris |
Archives