From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Sachin P. Sant" <sachinp@in.ibm.com>
Cc: Mel Gorman <mel@csn.ul.ie>,
linuxppc-dev@ozlabs.org,
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Subject: Re: [PowerPC] 2.6.29-rc3-git4 build break : truncated relocation
Date: Tue, 03 Feb 2009 20:28:53 +1100 [thread overview]
Message-ID: <1233653333.16867.85.camel@pasglop> (raw)
In-Reply-To: <49880C42.8060702@in.ibm.com>
On Tue, 2009-02-03 at 14:50 +0530, Sachin P. Sant wrote:
> 2.6.29-rc3-git4 allyesconfig build breaks with following error
I think it's the recurrent problem of allyesconfig generating a kernel
too big for our linker especially when ftrace is enabled.
We need to see if it's worth the pain of working around it with the
toolchain guys. Probably not tho...
Ben.
next prev parent reply other threads:[~2009-02-03 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 9:20 [PowerPC] 2.6.29-rc3-git4 build break : truncated relocation Sachin P. Sant
2009-02-03 9:28 ` Benjamin Herrenschmidt [this message]
2009-02-03 10:03 ` Stephen Rothwell
2009-02-03 10:36 ` Sachin P. Sant
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=1233653333.16867.85.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=mel@csn.ul.ie \
--cc=sachinp@in.ibm.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).