public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fernando Rodriguez <frodriguez.developer@outlook.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Will a 64-bit-no-multilib machine cross-compile 32-bit code?
Date: Wed, 18 Mar 2015 22:27:05 -0400	[thread overview]
Message-ID: <2685505.RfjHhG2H7t@navi> (raw)
In-Reply-To: <20150319015612.GA7416@waltdnes.org>

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

On Wednesday, March 18, 2015 9:56:12 PM 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've done it with distcc by adding the -m32 option to cflags. I used a script 
(named after the compiler on the gentoo box) to call the compiler with the -
m32 flag and placed on the PATH environment (just for the distccd service) 
before anything else and it worked. I got a 64 bit arch box to compile for a 
32 bit gentoo (not nearly as fast as compiling locally on the arch box but 
much faster than the gentoo box). It should work similarly with other cross-
compile scenarios.


-- 
Fernando Rodriguez

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-03-19  2:27 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-19  1:56 [gentoo-user] Will a 64-bit-no-multilib machine cross-compile 32-bit code? Walter Dnes
2015-03-19  2:27 ` Fernando Rodriguez [this message]
2015-03-19  4:20   ` Walter Dnes
2015-03-19  5:12     ` Fernando Rodriguez
2015-03-21 12:46     ` Mike Gilbert
2015-03-21 19:52       ` Fernando Rodriguez
2015-03-22 14:03         ` Mike Gilbert
2015-03-22 14:05           ` Mike Gilbert
2015-03-23  0:56           ` Fernando Rodriguez
2015-03-23  1:25           ` Fernando Rodriguez
2015-03-24  1:51             ` Walter Dnes
2015-03-23 22:18               ` Mike Gilbert
2015-03-23 22:41                 ` Fernando Rodriguez
2015-03-23 22:48                   ` Mike Gilbert
2015-03-24  0:37                     ` Fernando Rodriguez
2015-03-24  6:06                   ` Walter Dnes
2015-03-24  7:17                 ` Walter Dnes
2015-03-24 17:18                   ` Mike Gilbert
2015-03-24 19:01                   ` Fernando Rodriguez
2015-03-25  2:01                     ` Walter Dnes
2015-03-25  5:20                     ` Walter Dnes
2015-03-25  6:44                       ` Walter Dnes
2015-03-24  0:26               ` Peter Humphrey
2015-03-22 11:32       ` Walter Dnes
2015-03-28 11:13 ` Frank Steinmetzger
2015-03-28 13:03   ` Walter Dnes

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2685505.RfjHhG2H7t@navi \
    --to=frodriguez.developer@outlook.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox