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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Christoph,

On Thu, 6 Nov 2008 13:15:07 -0600 (CST) Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx> 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'

-- 
Cheers,
Stephen Rothwell                    sfr@xxxxxxxxxxxxxxxx
http://www.canb.auug.org.au/~sfr/

Attachment: pgpWuTTUu3DWi.pgp
Description: PGP signature


[Index of Archives]     [Linux Kernel]     [Linux USB Development]     [Yosemite News]     [Linux SCSI]

  Powered by Linux