From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
by finch.gentoo.org with esmtp (Exim 4.60)
(envelope-from <gentoo-embedded+bounces-3263-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1NGEEz-0007op-Jl
for garchives@archives.gentoo.org; Thu, 03 Dec 2009 16:09:13 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 62A2EE082F
for <garchives@archives.gentoo.org>; Thu, 3 Dec 2009 16:09:12 +0000 (UTC)
Received: from mail-fx0-f217.google.com (mail-fx0-f217.google.com [209.85.220.217])
by pigeon.gentoo.org (Postfix) with ESMTP id E22C1E0864
for <gentoo-embedded@lists.gentoo.org>; Thu, 3 Dec 2009 14:21:55 +0000 (UTC)
Received: by fxm9 with SMTP id 9so1350180fxm.10
for <gentoo-embedded@lists.gentoo.org>; Thu, 03 Dec 2009 06:21:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:in-reply-to:references
:from:date:message-id:subject:to:content-type;
bh=pJAtsNzxWMD0nE0pAv1OtitZFgZfgvWbwnJZ6qhUO10=;
b=Us/hvp/Q4rPJ15uZ/ew9PuGH3ydCs3sPnQdS9i3B5BhgcAnxLwP2k/Og6PsIagtZs0
OI3LBKaspyrbBrvl4zllMD3gKERBL85rjZKcfGUgazqwZfoszsL8Fbz50htSdw6SBQZX
YHcjLqw+nQtWMreTMVnTkQCtM1cjAWhNi28lE=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:from:date:message-id:subject:to
:content-type;
b=daL2IgSefxFuVtwLYW57G54IN+cT4JSLmv/j1Qu9JBW+PTVgfGNnH2acta4jPReEXF
CSS7Qx3HVFm8YOlFBbN8T+xlcjeklFV3zcc2dLYf8Fx89LWzq6h97cBjzYu/Ar9uJvb9
jhU/VImr9NsE3+YKm68c1BP1X9w3/JyEMVZKc=
Precedence: bulk
List-Post: <mailto:gentoo-embedded@lists.gentoo.org>
List-Help: <mailto:gentoo-embedded+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-embedded+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-embedded+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-embedded.gentoo.org>
X-BeenThere: gentoo-embedded@lists.gentoo.org
Reply-to: gentoo-embedded@lists.gentoo.org
MIME-Version: 1.0
Received: by 10.223.77.141 with SMTP id g13mr269720fak.0.1259850115091; Thu,
03 Dec 2009 06:21:55 -0800 (PST)
In-Reply-To: <20091202200422.4470.qmail@stuge.se>
References: <166af1cf0912020946g110c8d53ib1d844a5b370d7b7@mail.gmail.com>
<20091202200422.4470.qmail@stuge.se>
From: Shinkan <shinkan@gmail.com>
Date: Thu, 3 Dec 2009 15:21:35 +0100
Message-ID: <166af1cf0912030621g56dafb57wbd16eaf95485b37@mail.gmail.com>
Subject: Re: [gentoo-embedded] Cross emerging to a given root.
To: gentoo-embedded@lists.gentoo.org
Content-Type: multipart/alternative; boundary=0015174792d6948e140479d3b6b3
X-Archives-Salt: 01bc95eb-c3c8-4bd8-9b37-30d08edc59b9
X-Archives-Hash: b6debe6d68bf84c4007dcba755828534
--0015174792d6948e140479d3b6b3
Content-Type: text/plain; charset=UTF-8
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
--0015174792d6948e140479d3b6b3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<br><br><div class=3D"gmail_quote">2009/12/2 Peter Stuge <span dir=3D"ltr">=
<<a href=3D"mailto:peter@stuge.se">peter@stuge.se</a>></span><br><blo=
ckquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, 204,=
204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class=3D"im">Shinkan wrote:<br>
> to compile with given versions of glibc/binutils, to be sure that<br>
> some bins will run on my target system.<br>
><br>
> 1) Is there any other way to do that without emerging a<br>
> cross-compiler on my host ?<br>
<br>
</div>You could do it for the toolchain, and use eselect to pick which one<=
br>
should be active. For libc, I don't think it's possible.<br>
<div class=3D"im"><font color=3D"#888888"><br></font></div></blockquote><di=
v><br>In fact I noticed I don't really need cross dev.<br>So I just eme=
rged GCC 3.4 (my host is compiled with 4.3), gcc-config selected it.<br>Wou=
ld that be sufficient to build my target (by doing emerge --root=3D/mytarge=
t --config-root=3D/myconfig system) en ensure my target will run GCC 3.4 co=
mpiled binaries ?<br>
<br>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++.<br>What could I do to fix that ?<br></div></div>
<br><br>-- <br>Pierre.<br>"Sometimes when I'm talking, my words ca=
n't keep up with my thoughts. I wonder why we think faster than we spea=
k. Probably so we can think twice." - Bill Watterson<br>
--0015174792d6948e140479d3b6b3--