From: Shinkan <shinkan@gmail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] Cross emerging to a given root.
Date: Thu, 3 Dec 2009 15:21:35 +0100 [thread overview]
Message-ID: <166af1cf0912030621g56dafb57wbd16eaf95485b37@mail.gmail.com> (raw)
In-Reply-To: <20091202200422.4470.qmail@stuge.se>
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
2009/12/2 Peter Stuge <peter@stuge.se>
> Shinkan wrote:
> > 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 ?
>
> You could do it for the toolchain, and use eselect to pick which one
> should be active. For libc, I don't think it's possible.
>
>
In fact I noticed I don't really need cross dev.
So I just emerged GCC 3.4 (my host is compiled with 4.3), gcc-config
selected it.
Would that be sufficient to build my target (by doing emerge
--root=/mytarget --config-root=/myconfig system) en ensure my target will
run GCC 3.4 compiled binaries ?
I tested it and emerge failed on some ports because installing them use
binaries that complain about not finding required versions of "CXXABI" or so
in libstdc++.
What could I do to fix that ?
--
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: 1539 bytes --]
next prev parent reply other threads:[~2009-12-03 16:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 17:46 [gentoo-embedded] Cross emerging to a given root Shinkan
2009-12-02 20:04 ` Peter Stuge
2009-12-03 14:21 ` Shinkan [this message]
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=166af1cf0912030621g56dafb57wbd16eaf95485b37@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