linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: 440 ebony patch seems to have broken 85xx build on powerpc.git
Date: Fri, 25 May 2007 00:03:58 +0200	[thread overview]
Message-ID: <e8cd495a755ca9e5a9d9976f21db1387@kernel.crashing.org> (raw)
In-Reply-To: <1180038295.3360.29.camel@zod.rchland.ibm.com>

> Yeah, it's finding those combinations that work for all the existing
> toolchains out there that's the issue.

No, it was a simple bug -- we shouldn't pass an assembler
flag for 440.o and ebony.o, but a compiler flag.


Segher

  parent reply	other threads:[~2007-05-24 22:04 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-24 17:13 440 ebony patch seems to have broken 85xx build on powerpc.git Dave Jiang
2007-05-24 17:37 ` Josh Boyer
2007-05-24 17:43   ` Dave Jiang
2007-05-24 18:02 ` Sergei Shtylyov
2007-05-24 18:09   ` Josh Boyer
2007-05-25  1:27     ` David Gibson
2007-05-24 19:05 ` Segher Boessenkool
2007-05-24 19:39   ` Josh Boyer
2007-05-24 20:18     ` Segher Boessenkool
2007-05-24 20:21     ` Arnd Bergmann
2007-05-24 20:24       ` Josh Boyer
2007-05-24 21:07         ` Mark A. Greer
2007-05-24 21:16         ` Arnd Bergmann
2007-05-24 22:08           ` Segher Boessenkool
2007-05-24 22:03         ` Segher Boessenkool [this message]
2007-05-24 22:02       ` Segher Boessenkool
2007-05-25  1:30         ` David Gibson
2007-05-25 14:01           ` Segher Boessenkool
2007-05-24 22:09   ` Segher Boessenkool

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=e8cd495a755ca9e5a9d9976f21db1387@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=arnd@arndb.de \
    --cc=jwboyer@linux.vnet.ibm.com \
    --cc=linuxppc-dev@ozlabs.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).