* linux-next: build failure
@ 2008-10-16 9:29 Stephen Rothwell
2008-10-16 10:39 ` Ingo Molnar
0 siblings, 1 reply; 6+ messages in thread
From: Stephen Rothwell @ 2008-10-16 9:29 UTC (permalink / raw)
To: Jeremy Fitzhardinge; +Cc: Ingo, ppc-dev, Molnar, linux-next, Andrew Morton
Hi all,
Today's linux-next build (powerpc allyesconfig) failed like this:
In file included from arch/powerpc/include/asm/mmu-hash64.h:17,
from arch/powerpc/include/asm/mmu.h:8,
from arch/powerpc/include/asm/pgtable.h:8,
from arch/powerpc/mm/slb.c:20:
arch/powerpc/include/asm/page.h:76: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'memstart_addr'
arch/powerpc/include/asm/page.h:77: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'kernstart_addr'
Caused by commit 600715dcdf567c86f8b2c6173fcfb4b873e25a19 ("generic: add
phys_addr_t for holding physical addresses") from the tip-core tree.
This only fails if CONFIG_RELOCATABLE is set.
I have applied the patch below.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
>From 3e3a6a5f9479a4d35070c15f863a8635e9865058 Mon Sep 17 00:00:00 2001
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Thu, 16 Oct 2008 20:07:00 +1100
Subject: [PATCH] tip-core/powerpc: phys_addr_t has moved to linux/types.h
So include that instead of asm/types.h in asm/page.h for
the CONFIG_RELOCATABLE case.
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
arch/powerpc/include/asm/page.h | 6 +++++-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/arch/powerpc/include/asm/page.h b/arch/powerpc/include/asm/page.h
index 64e1445..5ac51e6 100644
--- a/arch/powerpc/include/asm/page.h
+++ b/arch/powerpc/include/asm/page.h
@@ -10,9 +10,13 @@
* 2 of the License, or (at your option) any later version.
*/
+#ifndef __ASSEMBLY__
+#include <linux/types.h>
+#else
+#include <asm/types.h>
+#endif
#include <asm/asm-compat.h>
#include <asm/kdump.h>
-#include <asm/types.h>
/*
* On PPC32 page size is 4K. For PPC64 we support either 4K or 64K software
--
1.5.6.5
^ permalink raw reply related [flat|nested] 6+ messages in thread
* Re: linux-next: build failure
2008-10-16 9:29 linux-next: build failure Stephen Rothwell
@ 2008-10-16 10:39 ` Ingo Molnar
2008-10-16 16:11 ` Jeremy Fitzhardinge
0 siblings, 1 reply; 6+ messages in thread
From: Ingo Molnar @ 2008-10-16 10:39 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: ppc-dev, Jeremy Fitzhardinge, linux-next, Andrew Morton
* Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> Today's linux-next build (powerpc allyesconfig) failed like this:
>
> In file included from arch/powerpc/include/asm/mmu-hash64.h:17,
> from arch/powerpc/include/asm/mmu.h:8,
> from arch/powerpc/include/asm/pgtable.h:8,
> from arch/powerpc/mm/slb.c:20:
> arch/powerpc/include/asm/page.h:76: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'memstart_addr'
> arch/powerpc/include/asm/page.h:77: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'kernstart_addr'
>
> Caused by commit 600715dcdf567c86f8b2c6173fcfb4b873e25a19 ("generic: add
> phys_addr_t for holding physical addresses") from the tip-core tree.
> This only fails if CONFIG_RELOCATABLE is set.
>
> I have applied the patch below.
applied to tip/core/urgent, thanks Stephen!
Ingo
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: linux-next: build failure
2008-10-16 10:39 ` Ingo Molnar
@ 2008-10-16 16:11 ` Jeremy Fitzhardinge
2008-10-16 16:14 ` Ingo Molnar
0 siblings, 1 reply; 6+ messages in thread
From: Jeremy Fitzhardinge @ 2008-10-16 16:11 UTC (permalink / raw)
To: Ingo Molnar; +Cc: Stephen Rothwell, Andrew Morton, linux-next, ppc-dev
Ingo Molnar wrote:
> * Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
>
>> Hi all,
>>
>> Today's linux-next build (powerpc allyesconfig) failed like this:
>>
>> In file included from arch/powerpc/include/asm/mmu-hash64.h:17,
>> from arch/powerpc/include/asm/mmu.h:8,
>> from arch/powerpc/include/asm/pgtable.h:8,
>> from arch/powerpc/mm/slb.c:20:
>> arch/powerpc/include/asm/page.h:76: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'memstart_addr'
>> arch/powerpc/include/asm/page.h:77: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'kernstart_addr'
>>
>> Caused by commit 600715dcdf567c86f8b2c6173fcfb4b873e25a19 ("generic: add
>> phys_addr_t for holding physical addresses") from the tip-core tree.
>> This only fails if CONFIG_RELOCATABLE is set.
>>
>> I have applied the patch below.
>>
>
> applied to tip/core/urgent, thanks Stephen!
>
Shouldn't this go via a ppc tree? Won't having ppc changes in tip.git
make people grumpy?
J
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: linux-next: build failure
2008-10-16 16:11 ` Jeremy Fitzhardinge
@ 2008-10-16 16:14 ` Ingo Molnar
0 siblings, 0 replies; 6+ messages in thread
From: Ingo Molnar @ 2008-10-16 16:14 UTC (permalink / raw)
To: Jeremy Fitzhardinge; +Cc: Stephen Rothwell, Andrew Morton, linux-next, ppc-dev
* Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> Ingo Molnar wrote:
>> * Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>>
>>
>>> Hi all,
>>>
>>> Today's linux-next build (powerpc allyesconfig) failed like this:
>>>
>>> In file included from arch/powerpc/include/asm/mmu-hash64.h:17,
>>> from arch/powerpc/include/asm/mmu.h:8,
>>> from arch/powerpc/include/asm/pgtable.h:8,
>>> from arch/powerpc/mm/slb.c:20:
>>> arch/powerpc/include/asm/page.h:76: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'memstart_addr'
>>> arch/powerpc/include/asm/page.h:77: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'kernstart_addr'
>>>
>>> Caused by commit 600715dcdf567c86f8b2c6173fcfb4b873e25a19 ("generic: add
>>> phys_addr_t for holding physical addresses") from the tip-core tree.
>>> This only fails if CONFIG_RELOCATABLE is set.
>>>
>>> I have applied the patch below.
>>>
>>
>> applied to tip/core/urgent, thanks Stephen!
>>
>
> Shouldn't this go via a ppc tree? Won't having ppc changes in tip.git
> make people grumpy?
it was broken via a generic topic: tip/core/resources, not the x86 tree.
Ingo
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: linux-next: build failure
2009-04-08 4:04 Stephen Rothwell
@ 2009-04-08 5:12 ` Alan Modra
0 siblings, 0 replies; 6+ messages in thread
From: Alan Modra @ 2009-04-08 5:12 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, Paul Mackerras, linuxppc-dev
On Wed, Apr 08, 2009 at 02:04:07PM +1000, Stephen Rothwell wrote:
> LD vmlinux.o
> powerpc-linux-ld: TOC section size exceeds 64k
I'm starting to sound like a cracked record, but I'll say it again:
ld -r does not merely package together object files, it transforms
them. Try using thin archives instead.
--
Alan Modra
Australia Development Lab, IBM
^ permalink raw reply [flat|nested] 6+ messages in thread
* linux-next: build failure
@ 2009-04-08 4:04 Stephen Rothwell
2009-04-08 5:12 ` Alan Modra
0 siblings, 1 reply; 6+ messages in thread
From: Stephen Rothwell @ 2009-04-08 4:04 UTC (permalink / raw)
To: Benjamin Herrenschmidt, Paul Mackerras; +Cc: linuxppc-dev, linux-next, amodra
[-- Attachment #1: Type: text/plain, Size: 330 bytes --]
Hi all,
Today's linux-next build (powerpc allyesconfig) failed like this:
LD vmlinux.o
powerpc-linux-ld: TOC section size exceeds 64k
I will think about (and appreciate suggestions on) how to fix this ...
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2009-04-08 5:12 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-10-16 9:29 linux-next: build failure Stephen Rothwell
2008-10-16 10:39 ` Ingo Molnar
2008-10-16 16:11 ` Jeremy Fitzhardinge
2008-10-16 16:14 ` Ingo Molnar
2009-04-08 4:04 Stephen Rothwell
2009-04-08 5:12 ` Alan Modra
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).