From: Angelo Arrifano <miknix@gentoo.org>
To: gentoo-embedded@lists.gentoo.org
Cc: jesse@boldandbusted.com
Subject: Re: [gentoo-embedded] "Gentoo on the Marvell Sheevaplug" Code Listing 3.6 question
Date: Sat, 26 Jun 2010 01:36:48 +0200 [thread overview]
Message-ID: <4C253D90.4090707@gentoo.org> (raw)
In-Reply-To: <1277506840.20491.1381949663@webmail.messagingengine.com>
On 26-06-2010 01:00, jesse@boldandbusted.com wrote:
> Howdy. I'd like to know how Gentoo devs build the files in Code Listing
> 3.6 in http://dev.gentoo.org/~armin76/arm/sheevaplug/install.xml ? I'd
> like to build those files myself, and would love to see your recipe,
> even if it's very rough. I'm especially interested in what tools you
> used. Thanks.
* uImage_kwplug is just Linux - the kernel. The sources are mainly
available on kernel.org. You need a cross compiler to build them for
this particular Marvell CPU. Look on Gentoo documentation how to build a
cross compiler and how to compile the kernel.
* sheevaplug.initramfs - This is just the bootable userspace. Since we
are at Gentoo, I guess it was produced using our cross-compiler
toolchain which is embedded in the Gentoo's package manager. Look on our
documentation how to build a cross compiler and cross compile with emerge.
Keywords: crossdev, emerge, cross root compilation, cross compile kernel
There are no secrets, everything is widely available
Have fun ;)
>
> Cheers,
> Jesse Adelman
> San Francisco, CA
>
next prev parent reply other threads:[~2010-06-26 0:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-25 23:00 [gentoo-embedded] "Gentoo on the Marvell Sheevaplug" Code Listing 3.6 question jesse
2010-06-25 23:36 ` Angelo Arrifano [this message]
2010-06-25 23:42 ` jesse
2010-06-26 0:01 ` Angelo Arrifano
2010-06-26 0:35 ` jesse
2010-06-29 18:05 ` Raúl Porcel
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=4C253D90.4090707@gentoo.org \
--to=miknix@gentoo.org \
--cc=gentoo-embedded@lists.gentoo.org \
--cc=jesse@boldandbusted.com \
/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