From: "Canek Peláez Valdés" <caneko@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Compiling for different CPU but same architecture
Date: Fri, 1 Aug 2014 00:46:31 -0500 [thread overview]
Message-ID: <CADPrc83nsfFYdQMCX37DhZT18ewfungC3H0UC6uEV_a37eO5UQ@mail.gmail.com> (raw)
In-Reply-To: <CAHgBc-vAb=FmT+fQ=gFFsR8NohZgWzm2m-ZgKOGH=Z8UDmRm2Q@mail.gmail.com>
On Thu, Jul 31, 2014 at 10:53 PM, Nilesh Govindrajan <me@nileshgr.com> wrote:
> What's the easiest way to compile Gentoo for another amd64 machine? I have a
> i5 desktop, and the laptop I have seems to be a subset of corei7 as per GCC
> native option.
> The basic installation was done using distcc, but it's not as fast as
> compiling completely on my machine. May be I should not put local host in
> distcc configuration? (It's a Pentium quad core 2.6 GHz).
If you have enough disk space, simply use a chroot with a copy of the
target /etc directory, and create binary packages that the target
machine can use by simply passing -k to emerge.
If you are using systemd, even better, use systemd-nswpan.
Regards.
--
Canek Peláez Valdés
Profesor de asignatura, Facultad de Ciencias
Universidad Nacional Autónoma de México
next prev parent reply other threads:[~2014-08-01 5:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 3:53 [gentoo-user] Compiling for different CPU but same architecture Nilesh Govindrajan
2014-08-01 5:46 ` Canek Peláez Valdés [this message]
2014-08-01 5:59 ` wraeth
2014-08-01 7:53 ` Neil Bothwick
2014-08-01 8:01 ` Nilesh Govindrajan
2014-08-01 8:09 ` Neil Bothwick
2014-08-01 8:23 ` wraeth
2014-08-01 8:25 ` Nilesh Govindrajan
2014-08-01 8:37 ` wraeth
2014-08-01 11:45 ` Jc García
2014-08-01 11:51 ` Neil Bothwick
2014-08-01 12:00 ` Jc García
2014-08-01 12:22 ` Nilesh Govindrajan
2014-08-01 13:04 ` Jc García
2014-08-01 12:29 ` Nilesh Govindrajan
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=CADPrc83nsfFYdQMCX37DhZT18ewfungC3H0UC6uEV_a37eO5UQ@mail.gmail.com \
--to=caneko@gmail.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