From: Shinkan <shinkan@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: [gentoo-embedded] Cross Dev Tricks + Hardened questions
Date: Mon, 30 Nov 2009 19:24:43 +0100 [thread overview]
Message-ID: <166af1cf0911301024s61e229a6h9116c00ad84673e8@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1943 bytes --]
Hi there,
I'm quite sorry to annoy you, but I'm quite new to Gentoo, and the Embedded
Handbook (which appears to be the best information source for what I want to
do) does not make it clear for me.
I hope you'll be able to help me a little.
I have a base host system, which is a x86 hardened-profiled Gentoo 10.0.
I would like to use it to build target systems with the most control Gentoo
can offer.
I first looked at Catalyst but Cross-dev things seemed more accurate for
what I want to do.
Let's say I want to make a "example-v1" target system.
I want my host to build on a "example-v1-build" directory everything needed
to build and emerge binaries for my target system.
I want my host to build with "example-v1-build" files and toolchain a
"example-v1-target" directory which would contain emerged system.
"example-v1-target" would contain a very minimal system, with no gcc, emerge
or dev things. It just have to be able to run C/C++ binaries for a given
arch.
I would like to use crossdev because I want to specify which version of
glibc/gcc/etc I will use for one given target.
Furthermore, I would like my toolchain to build "hardened" binaries, as
those we get by using an hardened stage3.
I don't get the process from the Embedded Handbook.
Do I have to set some CHOST, CTARGET, ROOT or PORTAGE_CONFDIR env vars or
crossdev will handle that some way ?
How can I tell to crossdev : "build the cross toolchain to my
example-v1-build directory" ?
How can I then tell to emerge "emerge and build from my example-v1-build
directory to example-v1-target" ? Do I have to chroot in "example-v1-build"
? In this case wouldn't I lost all emerge capabilities ?
Many thanks in advance for your help.
Sorry I can't figure it all by myself despite the good docs.
--
Pierre.
"Sometimes when I'm talking, my words can't keep up with my thoughts. I
wonder why we think faster than we speak. Probably so we can think twice." -
Bill Watterson
[-- Attachment #2: Type: text/html, Size: 2211 bytes --]
next reply other threads:[~2009-11-30 20:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-30 18:24 Shinkan [this message]
2009-11-30 21:12 ` [gentoo-embedded] Cross Dev Tricks + Hardened questions Peter Stuge
2009-12-01 8:44 ` Shinkan
2009-12-01 17:48 ` Ned Ludd
2009-12-01 19:03 ` Ed W
2009-12-01 20:51 ` Peter Stuge
2009-12-01 22:24 ` Shinkan
2009-12-02 0:17 ` Peter Stuge
2009-12-02 9:28 ` Shinkan
2009-12-01 19:03 ` Peter Stuge
2009-12-01 20:52 ` Shinkan
2009-12-01 23:57 ` Peter Stuge
2009-12-02 8:02 ` [OT] Catalyst, was: " Eckard Brauer
2009-12-02 9:04 ` Ed W
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=166af1cf0911301024s61e229a6h9116c00ad84673e8@mail.gmail.com \
--to=shinkan@gmail.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