All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karim Yaghmour <karim@opersys.com>
To: Lokesh Kumar <lokesh.kumar@wrx-us.com>
Cc: brian.auld@adic.com, linuxppc-embedded@lists.linuxppc.org
Subject: Re: x86(host) --> ppc(tgt) cross-tool-chain
Date: Fri, 06 Jun 2003 11:10:52 -0400	[thread overview]
Message-ID: <3EE0AEFC.8EA62FB0@opersys.com> (raw)
In-Reply-To: 3439AB3A99ECD5409F3A52ACF814744D158D22@norcom2.norcom.net


Lokesh Kumar wrote:
> I built the toolchain on x86 host for PPC, and I used
>
> GCC-2.95.3
> GLIBC-2.2.3
> Binutils-2.11.92
>
> I did not use Karim's book. I went with "Embedded Linux Interfacing ...."
> book.

:)

I have to ask: Did this toolchain actually work for you on the target?
I mean, did you try using glibc-2.2.3 on the PPC target? From I've
seen, gcc 2.95.3 with glibc 2.2.3 will successfully generate a glibc,
but the resulting glibc will core dump on the target.

Karim

--
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/

  reply	other threads:[~2003-06-06 15:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-06 15:00 x86(host) --> ppc(tgt) cross-tool-chain Lokesh Kumar
2003-06-06 15:10 ` Karim Yaghmour [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-09 12:17 Lokesh Kumar
2003-06-06 17:40 Lokesh Kumar
2003-06-07  2:13 ` Karim Yaghmour
2003-06-06 14:11 brian.auld
2003-06-06 14:33 ` Karim Yaghmour
2003-06-06 17:05 ` Magnus Damm
2003-06-06 17:14   ` Eugene Surovegin
2003-06-06 17:15   ` Matt Porter

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=3EE0AEFC.8EA62FB0@opersys.com \
    --to=karim@opersys.com \
    --cc=brian.auld@adic.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=lokesh.kumar@wrx-us.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.