[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0811061310350.6009@quilx.com>
Date: Thu, 6 Nov 2008 13:15:07 -0600 (CST)
From: Christoph Lameter <cl@...ux-foundation.org>
To: Alexey Dobriyan <adobriyan@...il.com>
cc: Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
rusty@...tcorp.com.au
Subject: Re: next-20081106: undefined reference to `__per_cpu_start'
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?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists