On Sun, Jul 31, 2016 at 07:40:37PM +0100, Mick wrote:
>
> * ARCH is not set... Are you missing the '/usr/i686-pc-linux-
> * gnu/etc/portage/make.profile' symlink? Is the symlink correct? Is your
> * portage tree complete?
> ===============
>
> As far as I can tell the link is there:
>
> # ls -la /usr/i686-pc-linux-gnu/etc/portage/
> total 8
> drwxr-xr-x 1 root root 56 Jul 31 19:32 .
> drwxr-xr-x 1 root root 20 Jul 31 18:32 ..
> -rw-r--r-- 1 root root 1019 Jul 31 19:32 make.conf
> lrwxrwxrwx 1 root root 30 Jul 31 17:48 make.profile ->
> /usr/portage/profiles/embedded
> drwxr-xr-x 1 root root 32 Jul 31 18:16 profile
>
> and it was created when I ran 'crossdev --stable -v -t i686-pc-linux-gnu'.
>
As far as I know, ARCH is one of those variables that has to be specified
in a profile, not in make.conf. A quick solution is to place the
ARCH=x86
line into the site-specific override .../etc/portage/profile/make.defaults
Although in this case your choice of profile may simply be wrong. The
embedded profile is the crossdev default that pretty much only has
busybox. Choose something like default/linux/x86/13.0 or if you want a lighter
libc how about default/linux/uclibc/x86 (or hardened/linux/musl/x86). That
should give you a more complete @system set.
>
> What am I missing? How would/do you go about achieving the same objective?
>
Since you are doing this on an amd64 box which can natively run x86, if
you want to achieve the same goal faster, start with a x86 stage3, chroot
into it and emerge a couple packages that you want to add, then tar it up
and load onto your 32 bit box. If you want to add packages later, emerge
them with '-b' in the chroot (on the amd64 box), and then follow
https://wiki.gentoo.org/wiki/Binary_package_guide
to allow the 32-bit box to install them as binary packages.
Ofcourse if you want to learn crossdev, then this is a great chance to do
so.
