From: Wolfgang Denk <wd@denx.de>
To: Dave Strout <dstrout@linuxfoundary.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Basics -- what tools for Walnut?
Date: Wed, 05 Jun 2002 21:16:33 +0200 [thread overview]
Message-ID: <20020605191638.298B0102F2@denx.denx.de> (raw)
In-Reply-To: Your message of "Wed, 05 Jun 2002 13:36:58 EDT." <3CFE4C3A.4070604@linuxfoundary.com>
In message <3CFE4C3A.4070604@linuxfoundary.com> you wrote:
>
> I think I'm missing a basic concept here -- I'm about to do some work on
> a Walnut system, so I started by loading up the HardHat Linux that came
> with the Walnut onto my intel desktop, then grabbing the
> linuxppc_2_4_devel kernel via rsync. When I try to compile, gas startes
> to complain about "unknown option '-m405'".
...
> So, is there a patch I should be applying before building the
> cross-compile environment, or a specific set of tools somewhere, or what
> am I missing?
Have a look at our ELDK, see http://www.denx.de/ELDK/
We support a couple of 405 boards (although the walnut is not one of
those).
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
"Faith: not *wanting* to know what is true." - Friedrich Nietzsche
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-06-05 19:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-05 17:36 Basics -- what tools for Walnut? Dave Strout
2002-06-05 17:43 ` Mark Hatle
2002-06-05 17:49 ` Frank Rowand
2002-06-05 18:14 ` Dan Malek
2002-06-05 18:24 ` Dave Strout
2002-06-05 19:16 ` Wolfgang Denk [this message]
2002-06-05 20:16 ` Can compile, now on to booting Dave Strout
2002-06-06 4:06 ` Donald White
2002-06-06 13:00 ` Dave Strout
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=20020605191638.298B0102F2@denx.denx.de \
--to=wd@denx.de \
--cc=dstrout@linuxfoundary.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).