linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Mark Hatle <fray@mvista.com>
To: Dave Strout <dstrout@linuxfoundary.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Basics -- what tools for Walnut?
Date: Wed, 05 Jun 2002 12:43:44 -0500	[thread overview]
Message-ID: <3CFE4DD0.7FC2E7BF@mvista.com> (raw)
In-Reply-To: 3CFE4C3A.4070604@linuxfoundary.com


The version of HardHat Linux that came with your walnut was created to match the
requirements of the kernel also shipped with Hard Hat Linux.

The current _devel kernel requires a newer version of binutils that understands
the -m405 architecture.  Either use the kernel shipped w/ Hard Hat Linux, or you
will need to get a newer tool chain.  (Either build it yourself or purchase it
from MontaVista...)

--Mark
(Speaking for myself, not MontaVista whom I work for.)

Dave Strout 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'".
>
> I tried running /opt/hardhat/devkit/ppc/4xx/bin/ppc_4xx-as -m405, and
> sure enough, it doesn't know the 405.  Nor does the gas that I built
> from binutils 2.10.1 with --target-powerpc.
>
> 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?
>
> thanks,
> dave.
>

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-06-05 17:43 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 [this message]
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
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=3CFE4DD0.7FC2E7BF@mvista.com \
    --to=fray@mvista.com \
    --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).