LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Christoph Lameter <cl@linux-foundation.org>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	rusty@rustcorp.com.au, Haavard Skinnemoen <hskinnemoen@atmel.com>
Subject: Re: next-20081106: undefined reference to `__per_cpu_start'
Date: Wed, 12 Nov 2008 08:59:55 +0100 (CET)	[thread overview]
Message-ID: <Pine.LNX.4.64.0811120859160.13217@anakin> (raw)
In-Reply-To: <20081107162114.2a41c623.sfr@canb.auug.org.au>

On Fri, 7 Nov 2008, Stephen Rothwell wrote:
> On Thu, 6 Nov 2008 13:15:07 -0600 (CST) Christoph Lameter <cl@linux-foundation.org> 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'

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

  parent reply	other threads:[~2008-11-12  8:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-06  6:36 linux-next: Tree for November 6 Stephen Rothwell
2008-11-06 18:39 ` next-20081106: undefined reference to `__per_cpu_start' Alexey Dobriyan
2008-11-06 19:15   ` Christoph Lameter
2008-11-06 22:34     ` Alexey Dobriyan
2008-11-07 18:32       ` Christoph Lameter
2008-11-07  5:21     ` Stephen Rothwell
2008-11-07  5:44       ` Alexey Dobriyan
2008-11-07 18:28         ` Christoph Lameter
2008-11-07 18:40       ` Christoph Lameter
2008-11-18  4:33         ` linux-next: cpu_alloc tree patch (Was: Re: next-20081106: undefined reference to `__per_cpu_start') Stephen Rothwell
2008-11-19 19:18           ` Christoph Lameter
2008-11-12  7:59       ` Geert Uytterhoeven [this message]
2008-11-12 11:18         ` next-20081106: undefined reference to `__per_cpu_start' Mike Frysinger
2008-11-06 18:54 ` next-20081106: perfmon on ia64 Alexey Dobriyan
2008-11-06 20:44   ` stephane eranian
2008-11-06 19:44 ` next-20081106: today's ftrace episode Alexey Dobriyan
2008-11-06 20:03   ` Steven Rostedt
2008-11-06 20:15     ` Alexey Dobriyan
2008-11-06 20:28       ` Steven Rostedt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0811120859160.13217@anakin \
    --to=geert@linux-m68k.org \
    --cc=adobriyan@gmail.com \
    --cc=cl@linux-foundation.org \
    --cc=hskinnemoen@atmel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).