linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: linuxppc-dev@ozlabs.org, tony@bakeyournoodle.com
Subject: Re: build failure with current linus tree
Date: Wed, 10 Sep 2008 01:56:26 +0200	[thread overview]
Message-ID: <20080909235626.GA5254@lst.de> (raw)
In-Reply-To: <20080905010618.GA30278@lst.de>

On Fri, Sep 05, 2008 at 03:06:18AM +0200, Christoph Hellwig wrote:
> Current linus tree fail to build for me for a 64bit powerpc config with:

This is cause by

commit 7563dc64585324f443f5ac107eb6d89ee813a2d2
Author: Tony Breeds <tony@bakeyournoodle.com>
Date:   Tue Sep 2 16:50:38 2008 +1000

    powerpc: Work around gcc's -fno-omit-frame-pointer bug

  reply	other threads:[~2008-09-09 23:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-05  1:06 build failure with current linus tree Christoph Hellwig
2008-09-09 23:56 ` Christoph Hellwig [this message]
2008-09-17 18:04   ` Chris Friesen
2008-09-17 18:44     ` Paul Mackerras

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=20080909235626.GA5254@lst.de \
    --to=hch@lst.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=tony@bakeyournoodle.com \
    /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).