From: Nilesh Govindrajan <me@nileshgr.com>
To: Gentoo User Mailing List <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:14:43 +0530 [thread overview]
Message-ID: <CAHgBc-uB0cRrB3xozBz-pXddH0SOm_nHysWeaLp5T5+PKZnfyA@mail.gmail.com> (raw)
In-Reply-To: <20130204063205.GA30347@dethkomp>
On Mon, Feb 4, 2013 at 12:02 PM, Yohan Pereira <yohan.pereira@gmail.com> wrote:
>
> I recently got a minimal gentoo running on the pi (without running
> emerge/compiling on the pi), here's what I've learned.
>
> Cross compilation is FUN <\sarcasm>. Lots of packages (like python)
> don't like being cross compiled. A good number of failures occurred
> because of missing build time dependencies on the host, Some times I had
> to copy certain files need at build-time from the host to the arm
> sysroot (mainly for the x11-proto/* packages).
>
> For the really adamant packages (like python) I used the method
> described here [1] to build binary packages using a native arm chroot +
> qemu-user (a rather interesting way to go about it).
>
> However I've not compared the performance (wrt compilation time) to
> running a full blown arm qemu vm so you may want to try that and see
> what works better for you. But I reckon any of these methods should be
> faster than compiling on the pi on a modern CPU.
>
> Also note cross-compiling is way faster than this method so I preferred
> cross-compiling and only resorted to this for packages like python.
>
> In the end I got it to boot. Then I decided I wanted to try xbmc, after
> seeing the long list of dependencies, I went ahead and installed
> openELEC :D. Which works great BTW (Still trying to find some indian
> news streams).
>
> [1] http://www.gentoo.org/proj/en/base/embedded/handbook/?part=1&chap=5
> (Note that page is a bit dated, app-emulation/qemu-user is masked in the
> tree. Use app-emulation/qemu instead)
>
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.
--
Nilesh Govindrajan
http://nileshgr.com
next prev parent reply other threads:[~2013-02-04 6:45 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 [this message]
2013-02-04 7:05 ` Yohan Pereira
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=CAHgBc-uB0cRrB3xozBz-pXddH0SOm_nHysWeaLp5T5+PKZnfyA@mail.gmail.com \
--to=me@nileshgr.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