public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Gregoire Favre <gregoire.favre@gmail.com>
Cc: linux-kernel@vger.kernel.org, Dave Jones <davej@codemonkey.org.uk>
Subject: Re: 2.6.17-mm4 undefined reference to `alternatives_smp_module_del'
Date: Thu, 29 Jun 2006 15:42:47 -0700	[thread overview]
Message-ID: <20060629154247.1bf8eccf.akpm@osdl.org> (raw)
In-Reply-To: <20060629122721.GA18671@gmail.com>

Gregoire Favre <gregoire.favre@gmail.com> wrote:
>
> Hello,
> 
> just tried to compil 2.6.17-mm4 under amd64 and it fails with :
> 
>   AR      arch/x86_64/lib/lib.a
>   GEN     .version
>   CHK     include/linux/compile.h
>   UPD     include/linux/compile.h
>   CC      init/version.o
>   LD      init/built-in.o
>   LD      .tmp_vmlinux1
> arch/x86_64/kernel/built-in.o: In function `module_arch_cleanup':
> (.text.module_arch_cleanup+0x1): undefined reference to `alternatives_smp_module_del'
> arch/x86_64/kernel/built-in.o: In function `module_finalize':
> (.text.module_finalize+0xe8): undefined reference to `alternatives_smp_module_add'
> make: *** [.tmp_vmlinux1] Error 1
> 
> 

Thanks.  Reverting
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.17/2.6.17-mm4/broken-out/x86-dont-print-out-smp-info-on-up-kernels.patch
will fix it.

<looks at davej>

That patch is pretty yuk anyway

 void module_arch_cleanup(struct module *mod)
 {
+#ifdef CONFIG_SMP
	alternatives_smp_module_del(mod);
+#endif
 }

Should be a stub in a header file, which would fix this problem too.

  reply	other threads:[~2006-06-29 22:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-29 12:27 2.6.17-mm4 undefined reference to `alternatives_smp_module_del' Gregoire Favre
2006-06-29 22:42 ` Andrew Morton [this message]
2006-06-29 23:24   ` Rene Herman
2006-06-29 23:40     ` Andrew Morton
2006-06-29 23:42       ` Dave Jones

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=20060629154247.1bf8eccf.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=davej@codemonkey.org.uk \
    --cc=gregoire.favre@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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