From: Karim Yaghmour <karim@opersys.com>
To: brian.auld@adic.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: x86(host) --> ppc(tgt) cross-tool-chain
Date: Fri, 06 Jun 2003 10:33:21 -0400 [thread overview]
Message-ID: <3EE0A631.D40DD19A@opersys.com> (raw)
In-Reply-To: 995FF289C9D69747A09E4299264459540C109867@penguin.adic.com
BTW, there's an ongoing thread about exactly this problem
on the embeddedTUX.org mailing list:
http://www.embeddedtux.org/pipermail/etux/2003-June/thread.html
Apparently you're not alone ...
Karim
brian.auld@adic.com wrote:
>
> Hello,
>
> Using Karim's new book "Building Embedded Linux Systems", has anyone out there successfully built an x86(host) --> ppc(tgt) tool chain using the versions stipulated in the book (gcc 2.95.3, binutils: 2.10.1, glibc, 2.2.1).
>
> If yes:
>
> (a) What host system are you using?
>
> (b) Did you diverge from the directions in the book?
>
> If no:
>
> (a) Can someone out there suggest a known valid combination?
>
> I anticipate needing ssh, some web-server and snmp as application requirements, so I figured it would be prudent to get the tool-chain working with glibc as opposed to uClibc.
>
> -- Brian
>
--
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 514-812-4145
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-06-06 14:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-06 14:11 x86(host) --> ppc(tgt) cross-tool-chain brian.auld
2003-06-06 14:33 ` Karim Yaghmour [this message]
2003-06-06 17:05 ` Magnus Damm
2003-06-06 17:14 ` Eugene Surovegin
2003-06-06 17:15 ` Matt Porter
-- strict thread matches above, loose matches on Subject: below --
2003-06-06 15:00 Lokesh Kumar
2003-06-06 15:10 ` Karim Yaghmour
2003-06-06 17:40 Lokesh Kumar
2003-06-07 2:13 ` Karim Yaghmour
2003-06-09 12:17 Lokesh Kumar
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=3EE0A631.D40DD19A@opersys.com \
--to=karim@opersys.com \
--cc=brian.auld@adic.com \
--cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).