From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] compiling via distcc
Date: Fri, 20 Feb 2015 06:51:49 +0300 [thread overview]
Message-ID: <20150220065149.c02dc75a15f95b94b1782f5c@gentoo.org> (raw)
In-Reply-To: <CAGymGEk2VQJXTg+OPuPavdiq3N76G4eqAMk2Y69A_v=kYiuJpg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]
On Wed, 11 Feb 2015 17:19:22 -0600 Jeff Smelser wrote:
> People do it all the time. You have to set up the amd64's to cross compile.
>
> https://wiki.gentoo.org/wiki/Distcc/Cross-Compiling
One doesn't need to setup cross-compilation in order to generate
x86 code on amd64 systems: 64-bit amd64 gcc natively supports this,
just be sure to add -m32 to your {C,CXX,F,FC,LD}FLAGS variables.
Care should be taken with -march=native or -mtune=native arguments.
Vanilla distcc doesn't support this. Patch can be taken here[1] or
distcc from my overlay[2] may be used.
Another approach will be to use one powerful box to build all
packages for an older system: either root filesystem may be
exported via NFS to a powerful host or just copy entire disk image
to and fro that host; afterwards just setarch && chroot to that
image / NFS mount and build all packages using modern hardware.
An old but still useful guide is here[3].
[1] https://groups.google.com/forum/#!topic/distcc-patches/eeP-9pTgz7E
[2] git://git.overlays.gentoo.org/dev/bircoph.git sys-devel/distcc
[3] http://www.gentoo-wiki.info/HOWTO_Emerge_on_very_slow_systems
Best regards,
Andrew Savchenko
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-02-20 23:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 22:51 [gentoo-user] compiling via distcc Joseph
2015-02-11 23:19 ` Jeff Smelser
2015-02-13 13:23 ` [gentoo-user] " James
2015-02-20 3:51 ` Andrew Savchenko [this message]
2015-02-21 9:48 ` [gentoo-user] " Peter Humphrey
2015-02-21 9:55 ` Peter Humphrey
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=20150220065149.c02dc75a15f95b94b1782f5c@gentoo.org \
--to=bircoph@gentoo.org \
--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