From: Boaz Harrosh <bharrosh@panasas.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
ppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: linux-next: Tree for August 5
Date: Wed, 05 Aug 2009 16:28:16 +0300 [thread overview]
Message-ID: <4A7988F0.2010208@panasas.com> (raw)
In-Reply-To: <20090805201336.fd2de2ad.sfr@canb.auug.org.au>
On 08/05/2009 01:13 PM, Stephen Rothwell wrote:
> Hi Boaz,
>
> On Wed, 05 Aug 2009 11:11:20 +0300 Boaz Harrosh <bharrosh@panasas.com> wrote:
>>
>> On 08/05/2009 10:23 AM, Stephen Rothwell wrote:
>>>
>>> This tree fails to build for powerpc allyesconfig (final link problem).
>>
>> Above is reported for a long time. Is it related to this:
>> http://www.spinics.net/lists/kernel/msg921978.html
>
> No, it is this:
>
> powerpc-linux-ld: TOC section size exceeds 64k
>
> It is powerpc specific and the only way we can think of fixing it
> involves stopping building the built-in.o files and linking the entire
> kernel in one go at the end. We just haven't had time (or the energy) to
> try to fix it properly while it only affects the final link of the
> allyesconfig kernel.
>
Ha, OK allyesconfig. Last time I attempted an allyesconfig for i386 I got
me the OOM killer attack on my KDE, half way into the final link.
That's why I use allmodconfig for when I need "try to compile everything ++"
I get just as much compilation coverage if not more. And is faster.
It'll not show symbol conflicts if any exist, though.
Thanks
Boaz
WARNING: multiple messages have this Message-ID (diff)
From: Boaz Harrosh <bharrosh@panasas.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org,
ppc-dev <linuxppc-dev@lists.ozlabs.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for August 5
Date: Wed, 05 Aug 2009 16:28:16 +0300 [thread overview]
Message-ID: <4A7988F0.2010208@panasas.com> (raw)
In-Reply-To: <20090805201336.fd2de2ad.sfr@canb.auug.org.au>
On 08/05/2009 01:13 PM, Stephen Rothwell wrote:
> Hi Boaz,
>
> On Wed, 05 Aug 2009 11:11:20 +0300 Boaz Harrosh <bharrosh@panasas.com> wrote:
>>
>> On 08/05/2009 10:23 AM, Stephen Rothwell wrote:
>>>
>>> This tree fails to build for powerpc allyesconfig (final link problem).
>>
>> Above is reported for a long time. Is it related to this:
>> http://www.spinics.net/lists/kernel/msg921978.html
>
> No, it is this:
>
> powerpc-linux-ld: TOC section size exceeds 64k
>
> It is powerpc specific and the only way we can think of fixing it
> involves stopping building the built-in.o files and linking the entire
> kernel in one go at the end. We just haven't had time (or the energy) to
> try to fix it properly while it only affects the final link of the
> allyesconfig kernel.
>
Ha, OK allyesconfig. Last time I attempted an allyesconfig for i386 I got
me the OOM killer attack on my KDE, half way into the final link.
That's why I use allmodconfig for when I need "try to compile everything ++"
I get just as much compilation coverage if not more. And is faster.
It'll not show symbol conflicts if any exist, though.
Thanks
Boaz
next prev parent reply other threads:[~2009-08-05 13:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-05 7:23 linux-next: Tree for August 5 Stephen Rothwell
2009-08-05 8:11 ` Boaz Harrosh
2009-08-05 10:13 ` Stephen Rothwell
2009-08-05 10:13 ` Stephen Rothwell
2009-08-05 10:13 ` Stephen Rothwell
2009-08-05 13:28 ` Boaz Harrosh [this message]
2009-08-05 13:28 ` Boaz Harrosh
2009-08-05 16:26 ` [PATCH -next] isdn: fix netjet build errors Randy Dunlap
2009-08-05 19:03 ` David Miller
2009-08-06 5:05 ` Karsten Keil
2009-08-06 20:10 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2010-08-05 4:04 linux-next: Tree for August 5 Stephen Rothwell
2008-08-05 7:59 Stephen Rothwell
2008-08-05 15:49 ` Stefan Richter
2008-08-05 15:55 ` David Woodhouse
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=4A7988F0.2010208@panasas.com \
--to=bharrosh@panasas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.