All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Christian Kujau <lists@nerdbynature.de>
Cc: LKML <linux-kernel@vger.kernel.org>, Trond.Myklebust@netapp.com
Subject: Re: undefined reference to `sys_nfsservctl'
Date: Mon, 29 Aug 2011 16:17:26 +1000	[thread overview]
Message-ID: <20110829161726.c980a80258fe714db49b425b@canb.auug.org.au> (raw)
In-Reply-To: <alpine.DEB.2.01.1108282138020.9183@trent.utfs.org>

[-- Attachment #1: Type: text/plain, Size: 962 bytes --]

Hi Christian,

On Sun, 28 Aug 2011 21:44:50 -0700 (PDT) Christian Kujau <lists@nerdbynature.de> wrote:
>
> When trying to compile 3.1-rc3 (git -c11a7e2), this happens after MODPOST:
> 
>   MODPOST vmlinux.o
> WARNING: modpost: Found 1 section mismatch(es).
> To see full details build your kernel with:
> 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
>   GEN     .version
>   CHK     include/generated/compile.h
>   UPD     include/generated/compile.h
>   CC      init/version.o
>   LD      init/built-in.o
>   LD      .tmp_vmlinux1
> arch/powerpc/kernel/built-in.o: In function `sys_call_table':
> (.text+0x5be0): undefined reference to `sys_nfsservctl'
> make[1]: *** [.tmp_vmlinux1] Error 1
> make: *** [sub-make] Error 2

I posted a patch to Linus earlier today (subject of lkml message:
"linux-next: build failure in Linus' tree").

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2011-08-29  6:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-29  4:44 undefined reference to `sys_nfsservctl' Christian Kujau
2011-08-29  6:17 ` Stephen Rothwell [this message]
2011-08-29 15:11   ` Christian Kujau
2011-08-31  4:38     ` Kumar Gala
2011-08-31  5:12       ` 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=20110829161726.c980a80258fe714db49b425b@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=Trond.Myklebust@netapp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@nerdbynature.de \
    /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.