maxime louvel wrote:
...
xmerge --root /home/newRoot baselayout glibc binutils
...
I assume this is pulling in a bunch of dependencies, including
findutils. Do you intend to build a full-blown system (no busybox) or a
minimal system (busybox and a few friends)? If you plan on using
busybox, then you want to xmerge that as well.
A good general rule of thumb (at least, it works for me ;-) ) is to
throw a '-pv' into each xmerge. eg:
xmerge --root /home/newRoot -pv baselayout glibc binutils
and see what it pulls in as dependencies. I then go to the top of the
list, let say baselayout is first, hypothetically. So I would then say:
xmerge --root /home/newRoot --nodeps baselayout
and then repeat for each package in the list that I actually want. Two
errors typically occur at this stage of the game.
1.) a missing runtime dependency, xmerge the dependency to newRoot.
2.) a missing compiletime dependency, xmerge the dependecy to SYSROOT.
The long and short of it is this: cross-compiling is a _much_ more acute
process, and it's best to take small steps through the initial build
than say 'xmerge --root $TGTROOT enlightenment' and hope for the best. :-)
hth,
Jason.
--
[email protected] mailing list
