From: Yohan Pereira <yohan.pereira@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Compiling Gentoo for Raspberry Pi (Was: List of base system packages)
Date: Mon, 4 Feb 2013 12:35:16 +0530 [thread overview]
Message-ID: <20130204070516.GA31427@dethkomp> (raw)
In-Reply-To: <CAHgBc-uB0cRrB3xozBz-pXddH0SOm_nHysWeaLp5T5+PKZnfyA@mail.gmail.com>
On 04/02/13 at 12:14pm, Nilesh Govindrajan wrote:
> Emulating the Pi on my machine would be slower since I have a dated
> E2180. It would be rather easier to get distcc on the Pi and make use
> of the 3 processors.
>
> But need to first figure out how to install emerge there...
> alternatively, could go with paludis which is written in C++, so the
> nagging python thing won't be there.
In that case why don't you just go ahead and use the stage 3 provided
for the pi? I know you said you didn't want to use it earlier, but
assuming your using the default profile to cross compile it will pull in
everything that's in the stage3 tarball anyway.
Once the stage 3 is setup you can use distcc and get rid of the stuff
you dont want.
Another thing you can do to speed things up is mount the root file
system over NFS or on a usb hdd. It was quite a bit faster in
my experience
--
- Yohan Pereira
The difference between a Miracle and a Fact is exactly the difference
between a mermaid and a seal.
-- Mark Twain
next prev parent reply other threads:[~2013-02-04 7:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-03 10:10 [gentoo-user] Compiling Gentoo for Raspberry Pi (Was: List of base system packages) Nilesh Govindrajan
2013-02-03 15:49 ` Dustin C. Hatch
2013-02-03 18:24 ` Nilesh Govindrajan
2013-02-03 21:44 ` Dustin C. Hatch
2013-02-04 5:43 ` Nilesh Govindrajan
2013-02-04 6:32 ` Yohan Pereira
2013-02-04 6:44 ` Nilesh Govindrajan
2013-02-04 7:05 ` Yohan Pereira [this message]
2013-02-04 13:23 ` Nilesh Govindrajan
2013-02-04 19:23 ` Dustin C. Hatch
2013-02-05 4:41 ` Nilesh Govindrajan
2013-02-05 5:09 ` Dustin C. Hatch
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=20130204070516.GA31427@dethkomp \
--to=yohan.pereira@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