From: Joshua ChaitinPollak <jpollak@kivasystems.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] trouble with emerging uclibc
Date: Mon, 20 Nov 2006 10:57:40 -0500 [thread overview]
Message-ID: <F415D554-E38B-45C1-A36E-52D97AB1C71B@kivasystems.com> (raw)
In-Reply-To: <200611200849.07056.corey@bitworthy.net>
On Nov 20, 2006, at 10:49 AM, Corey wrote:
> On Monday 20 November 2006 08:24, Josh Pollak wrote:
>> Hello, I'm having trouble building uclibc within a chroot
>> environment.
>>
>
> How did you build/create the chroot environment?
I use a series of custom shell scripts that basically follow the
TinyGentoo guide:
1) Get stage1-x868-uclibc-2005.0
2) Get today's portage snapshot
3) Set PROFILE=.../uclibc/x86 (should I use a subdirectory?)
4) run /usr/portage/scripts/bootstrap.sh
5) emerge -e system
And from there I build an embedded distribution using ROOT='/flash'
emerge .....
-Josh
--
Joshua ChaitinPollak
Software Engineer
Kiva Systems
--
gentoo-embedded@gentoo.org mailing list
next prev parent reply other threads:[~2006-11-20 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 15:24 [gentoo-embedded] trouble with emerging uclibc Josh Pollak
2006-11-20 15:49 ` Corey
2006-11-20 15:57 ` Joshua ChaitinPollak [this message]
2006-11-20 18:32 ` Corey
2006-11-26 23:37 ` Mike Frysinger
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=F415D554-E38B-45C1-A36E-52D97AB1C71B@kivasystems.com \
--to=jpollak@kivasystems.com \
--cc=gentoo-embedded@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