| 1 |
Ned Ludd schrieb: |
| 2 |
> On Wed, 2007-10-17 at 22:17 +0200, Marc Blumentritt wrote: |
| 3 |
>> Hi, |
| 4 |
>> |
| 5 |
>> I use ROOT and PORTAGE_CONFIGROOT to install an embedded system. But |
| 6 |
>> when I want to install certain packages, they pull in dependencies in my |
| 7 |
>> build system. An example is attached below |
| 8 |
>> (ROOT="/mediamachine/devroot"). Is this normal and why is this happening? |
| 9 |
> |
| 10 |
> |
| 11 |
> All dependencies must be meet on the host system. If they are not you |
| 12 |
> will get alot of bogus stuff pulled into your ROOT. |
| 13 |
> |
| 14 |
> This is why for ages I've been suggesting to people to first merge on / |
| 15 |
> then later using the -K option to sub merge into a new ROOT= so that |
| 16 |
> only the RDEPEND's will end up in $ROOT. |
| 17 |
|
| 18 |
What's the best approach, if I want to use different CFLAGS (especially |
| 19 |
march)? Use PORTAGE_CONFIGROOT (and -b) for building packages and then |
| 20 |
use ROOT and PORTAGE_CONFIGROOT (and -K) for merging with the embedded |
| 21 |
system? |
| 22 |
|
| 23 |
What about non-compilation stuff (e.g. passwd/shadow/group modifications |
| 24 |
or creation of dirs)? Is this done correctly if pre-built binary |
| 25 |
packages are used? |
| 26 |
|
| 27 |
Regards |
| 28 |
Marc |
| 29 |
|
| 30 |
-- |
| 31 |
gentoo-embedded@g.o mailing list |
Archives