From: Tom Rini <trini@kernel.crashing.org>
To: Giuliano Pochini <pochini@shiny.it>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: [PATCH][PPC32] Makefile cleanups and gcc-3.4+binutils-2.14 c
Date: Mon, 2 Aug 2004 08:43:12 -0700 [thread overview]
Message-ID: <20040802154312.GA4743@smtp.west.cox.net> (raw)
In-Reply-To: <20040731145303.26170308.pochini@shiny.it>
On Sat, Jul 31, 2004 at 02:53:03PM +0200, Giuliano Pochini wrote:
> On Fri, 30 Jul 2004 14:03:18 -0700
> Tom Rini <trini@kernel.crashing.org> wrote:
>
> >
> > On Fri, Jul 30, 2004 at 10:48:28PM +0200, Giuliano Pochini wrote:
> >
> > [snip]
> > > gcc 3.3.3 + binutils 2.15 fails quite soon here:
> > >
> > > AS arch/ppc/kernel/l2cr.o
> > > arch/ppc/kernel/l2cr.S: Assembler messages:
> > > arch/ppc/kernel/l2cr.S:110: Error: Unrecognized opcode: `dssall'
> > > arch/ppc/kernel/l2cr.S:278: Error: Unrecognized opcode: `dssall'
> > > arch/ppc/kernel/l2cr.S:387: Error: Unrecognized opcode: `dssall'
> > > make[1]: *** [arch/ppc/kernel/l2cr.o] Error 1
> >
> > Can you try with the following ?
> > [...]
>
> It doesn't apply to plain 2.6.7. What version I have to use ?
That was against then-current 2.6 bk, but might have been OK vs -rc2.
It is also part of now-current 2.6 bk, so if you can get that..
--
Tom Rini
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2004-08-02 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040728220733.GA16468@smtp.west.cox.net>
[not found] ` <XFMail.20040729100549.pochini@shiny.it>
[not found] ` <20040729144347.GE16468@smtp.west.cox.net>
[not found] ` <20040730205901.4d4181f4.pochini@shiny.it>
[not found] ` <20040730190731.GQ16468@smtp.west.cox.net>
[not found] ` <20040730224828.0f06e37a.pochini@shiny.it>
[not found] ` <20040730210318.GS16468@smtp.west.cox.net>
2004-07-31 12:53 ` [PATCH][PPC32] Makefile cleanups and gcc-3.4+binutils-2.14 c Giuliano Pochini
2004-08-02 15:43 ` Tom Rini [this message]
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=20040802154312.GA4743@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=pochini@shiny.it \
/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).