Date: Thu, 6 Nov 2008 13:15:07 -0600 (CST)
From: Christoph Lameter <cl@linux-foundation.org>
To: Alexey Dobriyan <adobriyan@gmail.com>
cc: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org,
       linux-kernel@vger.kernel.org, rusty@rustcorp.com.au
Subject: Re: next-20081106: undefined reference to `__per_cpu_start'
In-Reply-To: <20081106183939.GA26925@x200.localdomain>
Message-ID: <Pine.LNX.4.64.0811061310350.6009@quilx.com>
References: <20081106173645.e7e79071.sfr@canb.auug.org.au>
 <20081106183939.GA26925@x200.localdomain>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 997
Lines: 24

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/