| 1 |
maxime louvel wrote: |
| 2 |
... |
| 3 |
>> xmerge --root /home/newRoot baselayout glibc binutils |
| 4 |
... |
| 5 |
|
| 6 |
I assume this is pulling in a bunch of dependencies, including |
| 7 |
findutils. Do you intend to build a full-blown system (no busybox) or a |
| 8 |
minimal system (busybox and a few friends)? If you plan on using |
| 9 |
busybox, then you want to xmerge that as well. |
| 10 |
|
| 11 |
A good general rule of thumb (at least, it works for me ;-) ) is to |
| 12 |
throw a '-pv' into each xmerge. eg: |
| 13 |
|
| 14 |
xmerge --root /home/newRoot -pv baselayout glibc binutils |
| 15 |
|
| 16 |
and see what it pulls in as dependencies. I then go to the top of the |
| 17 |
list, let say baselayout is first, hypothetically. So I would then say: |
| 18 |
|
| 19 |
xmerge --root /home/newRoot --nodeps baselayout |
| 20 |
|
| 21 |
and then repeat for each package in the list that I actually want. Two |
| 22 |
errors typically occur at this stage of the game. |
| 23 |
|
| 24 |
1.) a missing runtime dependency, xmerge the dependency to newRoot. |
| 25 |
2.) a missing compiletime dependency, xmerge the dependecy to SYSROOT. |
| 26 |
|
| 27 |
The long and short of it is this: cross-compiling is a _much_ more acute |
| 28 |
process, and it's best to take small steps through the initial build |
| 29 |
than say 'xmerge --root $TGTROOT enlightenment' and hope for the best. :-) |
| 30 |
|
| 31 |
hth, |
| 32 |
|
| 33 |
Jason. |
| 34 |
-- |
| 35 |
gentoo-embedded@l.g.o mailing list |
Archives