linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: frowand@mvista.com
Cc: Dave Strout <dstrout@linuxfoundary.com>,
	linuxppc-embedded@lists.linuxppc.org
Subject: Re: Basics -- what tools for Walnut?
Date: Wed, 05 Jun 2002 14:14:14 -0400	[thread overview]
Message-ID: <3CFE54F6.1060605@embeddededge.com> (raw)
In-Reply-To: 3CFE4F42.DDB1D5CE@mvista.com


Frank Rowand wrote:

> I suspect that is a fairly old tool chain that you are using.

In the past, the practice was to inform people when changes were made
that required a minimum revision of tools to operate properly.
Simply telling people "your toolchain is too old" isn't helpful.....
What version of tools is required to build this properly?  Why
doesn't the check in comment indicate this information when the
change was made?

> Try modifying arch/ppc/Makefile to use
>
>   -mcpu=403

Or, just remove it since it doesn't perform any useful function.  On
the newer tools, it's required to allow the assembler to not bitch about
4xx unique instructions, another non-useful function, IMHO.

Thanks.

	-- Dan


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

  reply	other threads:[~2002-06-05 18:14 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 [this message]
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=3CFE54F6.1060605@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=dstrout@linuxfoundary.com \
    --cc=frowand@mvista.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).