1 |
On Sunday 18 March 2012 14:53:44 Joakim Tjernlund wrote: |
2 |
> What bugs me is that one can generally use /usr/$CTARGET as your root fs on |
3 |
> your favourite embedded target. Doing so will loose libgcc_s.so as there |
4 |
> isn't one installed. Having to install gcc into /usr/$CTARGET just to get |
5 |
> libgcc_s is a bit much. |
6 |
|
7 |
why does this actually matter ? as noted, this hack is merely there to |
8 |
support a split /usr setup. if you're using /usr/$CTARGET as your rootfs, |
9 |
then you aren't going to have a split /usr, and thus the lib copy is |
10 |
unnecessary. |
11 |
|
12 |
> Also, would it not be better if glibc showed up in |
13 |
> export ROOT=/usr/${CTARGET} PKGDIR=${PORTDIR}/pkgs/${CTARGET}/pkgs |
14 |
> quickpkg `qlist -IC` instead of |
15 |
> export ROOT=/ PKGDIR=${PORTDIR}/pkgs/${CTARGET}/cross-tools quickpkg |
16 |
> `qlist -IC cross-${CTARGET}` ? |
17 |
|
18 |
no. cross-${CTARGET}/glibc is a cross-compiler glibc, not a native one. yes, |
19 |
you can run it through a script to move things around so that it'd basically |
20 |
have the same install as a native glibc, but the existing one is not. |
21 |
|
22 |
it might be useful to have crossdev automatically inject glibc into |
23 |
package.provided for /usr/$CTARGET since attempting to install a native one in |
24 |
there will hit conflicts. |
25 |
-mike |