From: Matt Porter <porter@cox.net>
To: brian.auld@adic.com
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Kernel build: not recognizing 'tlbre' instruction
Date: Fri, 7 Feb 2003 14:01:16 -0700 [thread overview]
Message-ID: <20030207140116.B14341@home.com> (raw)
In-Reply-To: <995FF289C9D69747A09E42992644595405B23657@penguin.adic.com>; from brian.auld@adic.com on Fri, Feb 07, 2003 at 11:03:09AM -0800
On Fri, Feb 07, 2003 at 11:03:09AM -0800, brian.auld@adic.com wrote:
> (2) Regarding kernel tree without:
>
> ifdef CONFIG_4xx
> CFLAGS := $(CFLAGS) -Wa,-m405
> endif
>
> in arch/ppc/Makefile.
>
> The kernel trees that I have all have this set. Is the suggestion
> to comment this out, or find a kernel without it? If it's the latter,
> is there a nifty way to do this other than trial and error?
Guess that's not the problem, nm.
--
Matt Porter
porter@cox.net
This is Linux Country. On a quiet night, you can hear Windows reboot.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-02-07 21:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-07 19:03 Kernel build: not recognizing 'tlbre' instruction brian.auld
2003-02-07 21:01 ` Matt Porter [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-07 16:23 brian.auld
2003-02-07 17:02 ` Prakash kanthi
2003-02-07 17:33 ` 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=20030207140116.B14341@home.com \
--to=porter@cox.net \
--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).