From: Shinkan <shinkan@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: [gentoo-embedded] Cross emerging to a given root.
Date: Wed, 2 Dec 2009 18:46:17 +0100 [thread overview]
Message-ID: <166af1cf0912020946g110c8d53ib1d844a5b370d7b7@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
Hi again to all,
I emerged a cross-compiler on my host.
It's not to compile to a different arch than my host, but to compile with
given versions of glibc/binutils, to be sure that some bins will run on my
target system.
1) Is there any other way to do that without emerging a cross-compiler on my
host ?
When I try to cross-emerge bash on my target dir, it fails because it
doesn't find curses lib.
I fixed that by cross-emerging ncurses on /usr/$CTARGET, then retrying to
cross-emerge bash on my real target.
Is there any conf-based way of telling cross-emerge to look for its libs in
my real target and not on /usr/$CTARGET.
I want /usr/$CTARGET to just have the cross-compiler. I wants cros-emerged
suff to be somewhere else.
Thanks in advance.
--
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: 1036 bytes --]
next reply other threads:[~2009-12-02 18:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 17:46 Shinkan [this message]
2009-12-02 20:04 ` [gentoo-embedded] Cross emerging to a given root Peter Stuge
2009-12-03 14:21 ` Shinkan
2009-12-03 16:52 ` Ed W
2009-12-03 18:17 ` Shinkan
2009-12-03 23:23 ` Peter Stuge
2009-12-04 9:55 ` Ed W
2009-12-04 10:25 ` Peter Stuge
2009-12-03 23:19 ` Peter Stuge
2009-12-02 20:09 ` Ryan Tandy
2009-12-03 16:50 ` 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=166af1cf0912020946g110c8d53ib1d844a5b370d7b7@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