linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Alan Modra <amodra@bigpond.net.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: ppc-dev <linuxppc-dev@ozlabs.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Problems with allyesconfig kernel build
Date: Tue, 23 Oct 2007 19:49:01 +0930	[thread overview]
Message-ID: <20071023101900.GA21738@bubble.grove.modra.org> (raw)
In-Reply-To: <20071023140231.12698d1c.sfr@canb.auug.org.au>

On Tue, Oct 23, 2007 at 02:02:31PM +1000, Stephen Rothwell wrote:
> Anyone have any ideas?

The segfault with --emit-relocs and complaints about .fixup are linker
bugs.  I'm about the commit fixes for both of these problems.

-- 
Alan Modra
Australia Development Lab, IBM

      parent reply	other threads:[~2007-10-23 10:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-23  4:02 Problems with allyesconfig kernel build Stephen Rothwell
2007-10-23  4:07 ` Stephen Rothwell
2007-10-23  4:18 ` Andrew Morton
2007-10-23  4:47   ` Stephen Rothwell
2007-10-23  9:09 ` Segher Boessenkool
2007-10-23 10:19 ` Alan Modra [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=20071023101900.GA21738@bubble.grove.modra.org \
    --to=amodra@bigpond.net.au \
    --cc=akpm@linux-foundation.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sfr@canb.auug.org.au \
    /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).