Re: next-20081106: undefined reference to `__per_cpu_start'

From: Mike Frysinger
Date: Wed Nov 12 2008 - 06:18:39 EST


On Wed, Nov 12, 2008 at 02:59, Geert Uytterhoeven wrote:
> On Fri, 7 Nov 2008, Stephen Rothwell wrote:
>> On Thu, 6 Nov 2008 13:15:07 -0600 (CST) Christoph Lameter wrote:
>> > On Thu, 6 Nov 2008, Alexey Dobriyan wrote:
>> > > On blackfin-BF526-EZBRD and other blackfins:
>> > >
>> > > LD .tmp_vmlinux1
>> > > mm/built-in.o: In function `cpu_alloc_init':
>> > > (.init.text+0x1486): undefined reference to `__per_cpu_start'
>> > > mm/built-in.o: In function `cpu_alloc_init':
>> > > (.init.text+0x148c): undefined reference to `__per_cpu_start'
>> > > mm/built-in.o: In function `cpu_alloc_init':
>> > > (.init.text+0x1492): undefined reference to `__per_cpu_end'
>> > > mm/built-in.o: In function `cpu_alloc_init':
>> > > (.init.text+0x1496): undefined reference to `__per_cpu_end'
>> >
>> > Any contigencies for __per_cpu_start/end in your blackfin vmlinux.lds.h?
>> > That is where these symbols are defined
>> >
>> > Or did you use generic percpu support and set
>> > CONFIG_HAVE_ZERO_BASED_PER_CPU?
>>
>> Also a avr32 allnoconfig
>> (http://kisskb.ellerman.id.au/kisskb/buildresult/53233/) gets:
>>
>> backing-dev.c:(.init.text+0xc4c): undefined reference to `__per_cpu_start'
>> backing-dev.c:(.init.text+0xc50): undefined reference to `__per_cpu_end'
>>
>> and avr32 defconfig
>> (http://kisskb.ellerman.id.au/kisskb/buildresult/53225/) gets:
>>
>> vmstat.c:(.init.text+0xff0): undefined reference to `__per_cpu_start'
>> vmstat.c:(.init.text+0xff4): undefined reference to `__per_cpu_end'
>
> And m68k defconfig (http://kisskb.ellerman.id.au/kisskb/buildresult/54216/):
>
> | : undefined reference to `__per_cpu_start'
> | : undefined reference to `__per_cpu_end'

i already posted a patch:
http://lkml.org/lkml/2008/11/8/145
-mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/