Re: [gentoo-user] Will a 64-bit-no-multilib machine cross-compile 32-bit code?

[Frank Steinmetzger <Warp_7@gmx.de>]

[-- Attachment #1: Type: text/plain, Size: 1922 bytes --]

On Wed, Mar 18, 2015 at 09:56:12PM -0400, Walter Dnes wrote:
>   My situation...
> 
> * I've dug up my ancient netbook, and got Gentoo re-installed on it
> * The cpu is a dual-core Intel(R) Atom(TM) CPU Z520
> * It's 32-bit only; YES!
> * Compiling just the Seamonkey binary (ignoring its dependancies) took
>   14 hours
> 
>   I obviously want to offload compiling to another machine.  As per the
> subject, will a 64-bit no-multilb install be able to cross compile
> 32-bit code?

I recently did the first update after many months on my netbook, too. But I
choose the chroot path; using another linux, I tar'ed off the root
filesystem to an external disk and plugged that into my main rig. In there I
used the power of my might i5-4590 to do the upgrades. That's just that much
faster because many small packages use up minutes and minutes in the
configure and install phase. Not to mention hours spent of depend*e*ncy
calculations.

To quickly switch between building locally and via distcc (or chroot in this
case), I set up the usual march, CFLAGS, features, mirrors and such in
make.conf and then below that source my .conf file for distcc or chroot
which will override those settings. That way I only need to uncomment one
line in make.conf and I'm good to go.

Since there are different kinds of atoms, I also used the full range of
-mno- flags as given by `gcc -v -Q -march=native -O2 test.c -o test` and
because my Atom is 64 bit, but my userland 32, I manually added -m32 to
those. It went through in only a few hours for 500 packages including KDE.

The only problem I had was building the kernel. For some reason, I haven't
quite achieved coolness there yet with building it on my big machine.
-- 
Gruß | Greetings | Qapla’
Please do not share anything from, with or about me with any social network.

Thinking is work, work is energy and you should conserve energy.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]