Hello again, Still trying to form an image for deployment here.
Here are the commands I used: crossdev -S arm7a-hardfloat-linux-gnueabi emerge-wrapper --target armv7a-hardfloat-linux-gnueabi --init ROOT=/home/myuser/sysroots/board1 CHOST=x86_64-pc-linux-gnu armv7a-hardfloat-linux-gnueabi-emerge world This installs a few packages but I eventually get this error: >>> Emerging (24 of 248) sys-apps/baselayout-2.2::gentoo for /home/jc/sysroots/aw-som10/ * baselayout-2.2.tar.bz2 SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] * Your system profile has SYMLINK_LIB=yes, so that means you need to * have these paths configured as follows: * symlinks to 'lib64': /home/myuser/sysroots/board1/lib /home/myuser/sysroots/board1/usr/lib * The ebuild will attempt to fix these, but only for trivial conversions. * If things fail, you will need to manually create/move the directories. * Converting /home/myuser/sysroots/board1/lib from a dir to a symlink * ERROR: sys-apps/baselayout-2.2::gentoo failed (setup phase): * non-empty dir found where we needed a symlink: /home/myuser/sysroots/board1/lib Please, what is the proper method for generating a cross-compiled tree? Thanks On Thu, 2015-01-22 at 17:16 -0500, J (Jean-Claude Gervais) wrote: > Hi, > > I'm trying to put together a complete image for an arm board. > > Towards this end, I've used crossdev to generate a toolchain with the > following command: > > crossdev -S armv7a-hardfloat-linux-gnueabi > > Following the documentation, I'd like to use the emerge-wrapper tool but > the docs warn that I must first perform an "emerge-wrapper --init" > before attempting any package installations. > > When I run the "emerge-wrapper --init" command, it warns > > emerge-wrapper: missing --target <CHOST> option > > I'm still very much a newbie, so what is the correct usage? > > Thanks > >
