All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: "Sachin P. Sant" <sachinp@in.ibm.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	npiggin@suse.de, linuxppc-dev@ozlabs.org
Subject: Re: next Feb 10: mm/slqb build break
Date: Tue, 10 Feb 2009 13:53:51 +0200	[thread overview]
Message-ID: <84144f020902100353x4074f342ne4d61483074a06b7@mail.gmail.com> (raw)
In-Reply-To: <49914EE7.7030205@in.ibm.com>

On Tue, Feb 10, 2009 at 11:54 AM, Sachin P. Sant <sachinp@in.ibm.com> wrote:
> Sachin P. Sant wrote:
>>
>> Hi Stephen,
>>
>> Todays next randconfig build on powerpc fails with
>>
>>  CC      mm/slqb.o
>> mm/slqb.c: In function __slab_free:
>> mm/slqb.c:1648: error: implicit declaration of function
>> slab_free_to_remote
>> mm/slqb.c: In function kmem_cache_open:
>> mm/slqb.c:2174: error: implicit declaration of function
>> kmem_cache_dyn_array_free
>> mm/slqb.c:2175: warning: label error_cpu_array defined but not used
>> mm/slqb.c: In function kmem_cache_destroy:
>> mm/slqb.c:2294: error: implicit declaration of function
>> claim_remote_free_list
>> mm/slqb.c: In function kmem_cache_reap_percpu:
>> mm/slqb.c:2547: error: implicit declaration of function
>> flush_remote_free_cache
>> mm/slqb.c: In function kmem_cache_init:
>> mm/slqb.c:2783: error: per_cpu__kmem_cpu_nodes undeclared (first use in
>> this function)
>> mm/slqb.c:2783: error: (Each undeclared identifier is reported only once
>> mm/slqb.c:2783: error: for each function it appears in.)
>> mm/slqb.c:2784: error: kmem_cpu_cache undeclared (first use in this
>> function)
>> make[1]: *** [mm/slqb.o] Error 1
>> make: *** [mm] Error 2
>
> CONFIG_SMP is not set hence the failure.

Actually, that's not the root cause here. You seem to have CONFIG_SMP
disabled but CONFIG_NUMA enabled. That's not possible on x86 which
makes me think it's a ppc kconfig bug. Hmm?

                                                     Pekka

WARNING: multiple messages have this Message-ID (diff)
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: "Sachin P. Sant" <sachinp@in.ibm.com>
Cc: npiggin@suse.de, Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	linuxppc-dev@ozlabs.org
Subject: Re: next Feb 10: mm/slqb build break
Date: Tue, 10 Feb 2009 13:53:51 +0200	[thread overview]
Message-ID: <84144f020902100353x4074f342ne4d61483074a06b7@mail.gmail.com> (raw)
In-Reply-To: <49914EE7.7030205@in.ibm.com>

On Tue, Feb 10, 2009 at 11:54 AM, Sachin P. Sant <sachinp@in.ibm.com> wrote=
:
> Sachin P. Sant wrote:
>>
>> Hi Stephen,
>>
>> Todays next randconfig build on powerpc fails with
>>
>> =A0CC =A0 =A0 =A0mm/slqb.o
>> mm/slqb.c: In function __slab_free:
>> mm/slqb.c:1648: error: implicit declaration of function
>> slab_free_to_remote
>> mm/slqb.c: In function kmem_cache_open:
>> mm/slqb.c:2174: error: implicit declaration of function
>> kmem_cache_dyn_array_free
>> mm/slqb.c:2175: warning: label error_cpu_array defined but not used
>> mm/slqb.c: In function kmem_cache_destroy:
>> mm/slqb.c:2294: error: implicit declaration of function
>> claim_remote_free_list
>> mm/slqb.c: In function kmem_cache_reap_percpu:
>> mm/slqb.c:2547: error: implicit declaration of function
>> flush_remote_free_cache
>> mm/slqb.c: In function kmem_cache_init:
>> mm/slqb.c:2783: error: per_cpu__kmem_cpu_nodes undeclared (first use in
>> this function)
>> mm/slqb.c:2783: error: (Each undeclared identifier is reported only once
>> mm/slqb.c:2783: error: for each function it appears in.)
>> mm/slqb.c:2784: error: kmem_cpu_cache undeclared (first use in this
>> function)
>> make[1]: *** [mm/slqb.o] Error 1
>> make: *** [mm] Error 2
>
> CONFIG_SMP is not set hence the failure.

Actually, that's not the root cause here. You seem to have CONFIG_SMP
disabled but CONFIG_NUMA enabled. That's not possible on x86 which
makes me think it's a ppc kconfig bug. Hmm?

                                                     Pekka

  reply	other threads:[~2009-02-10 11:54 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10  8:41 linux-next: Tree for February 10 Stephen Rothwell
2009-02-10  9:23 ` next Feb 10: mm/slqb build break Sachin P. Sant
2009-02-10  9:54   ` Sachin P. Sant
2009-02-10 11:53     ` Pekka Enberg [this message]
2009-02-10 11:53       ` Pekka Enberg
2009-02-12  1:45       ` Nick Piggin
2009-02-12  1:45         ` Nick Piggin
2009-02-12  1:47         ` David Miller
2009-02-12  1:47           ` David Miller
2009-02-12 11:28         ` Sachin P. Sant
2009-02-12 11:28         ` Sachin P. Sant
2009-02-12 11:28         ` Sachin P. Sant
2009-02-12 11:28         ` Sachin P. Sant
2009-02-12 11:28           ` Sachin P. Sant
2009-02-10 10:30 ` Next Feb 10 : build/break arch/s390kernel.irq.o Sachin P. Sant
2009-02-10 11:15   ` [Patch] [s390] Fix init irq proc build break Sachin P. Sant
2009-02-10 11:40     ` Martin Schwidefsky
2009-02-10 10:45 ` Next Feb 10 build break on s390 : mm/shmem.c Sachin P. Sant
2009-02-10 13:40   ` Mimi Zohar
2009-02-10 19:55 ` linux-next: Tree for February 10 (security/audit/ima) Randy Dunlap
2009-02-10 22:40   ` Stephen Rothwell
2009-02-11  0:30     ` Mimi Zohar
2009-02-12 17:54       ` [PATCH -next] security/audit/ima: fix build error Randy Dunlap
2009-02-12 18:24         ` Mimi Zohar
2009-02-12 18:30           ` Randy Dunlap
2009-02-12 22:31         ` James Morris
2009-02-11  1:29   ` linux-next: Tree for February 10 (security/audit/ima) Al Viro
2009-02-11  2:27     ` Stephen Rothwell

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=84144f020902100353x4074f342ne4d61483074a06b7@mail.gmail.com \
    --to=penberg@cs.helsinki.fi \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=npiggin@suse.de \
    --cc=sachinp@in.ibm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.