1 |
Hi Corey |
2 |
> Thanks a ton for the helpful clues! |
3 |
> |
4 |
> I think I've almost got my mind wrapped around this stuff - but just to be |
5 |
> certain, I'd like to clarify one thing. |
6 |
> |
7 |
> My goal is pretty simple right now: I just want to create a second gentoo |
8 |
> installation on a separate partition, which is built from the ground-up using |
9 |
> uclibc - I'm still using the same platform/architecture ( i686 ), so I'm not |
10 |
> trying to target some different embedded device or anything, and I _do_ |
11 |
> want to have a complete toolchain ( including portage ) on this uclibc-based |
12 |
> gentoo partion. |
13 |
> |
14 |
> My intention/aim is to only cross-compile the minimal environment necessary |
15 |
> to be able to chroot into this new partition and begin emerging the rest of the |
16 |
> software I want, as per a normal/standard gentoo install. Restated, I'm simply |
17 |
> after a uclibc-based/built gentoo system. |
18 |
> |
19 |
> With that said, do I still need to emerge the libraries into a separate "SOMEXTOOLCHAIN" |
20 |
> ROOT? Or am I able to somehow just install those same libraries directly into |
21 |
> "YOUROTHERROOT" ROOT ( i.e., my separate partition, where I want my uclibc-based |
22 |
> gentoo to reside? ) |
23 |
> |
24 |
|
25 |
This depends mostly on your intentions and for sure on the packages |
26 |
options. If you have the choice, to statically compile the libs into the |
27 |
packages, then you don't need it in your minimal-root. This is an |
28 |
option, when the package has a static use flag. But if it has no option |
29 |
for static compiling, then the package needs to have the lib available |
30 |
because it uses the lib at runtime. For example, busybox supports static |
31 |
compiling and is able to run without any library, if you give it the |
32 |
static use flag. But be aware of other packages. Most of them don't |
33 |
support it. |
34 |
|
35 |
-daniel |
36 |
-- |
37 |
gentoo-embedded@g.o mailing list |