public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: <tigran.mkrtchyan@desy.de>
Cc: linux-nfs <linux-nfs@vger.kernel.org>
Subject: Re: failed to compile kernel due to object layout
Date: Wed, 9 Nov 2011 09:29:07 -0800	[thread overview]
Message-ID: <4EBAB863.1030303@panasas.com> (raw)
In-Reply-To: <CAGue13qr5iq=yhCA5BEzeoX94-ha7y4-fXMxH6C1g0nUia2Ceg@mail.gmail.com>

On 11/09/2011 02:48 AM, Tigran Mkrtchyan wrote:
> Hi Boaz,
> 
> did I miss configured something?
> 
> Kernel: arch/x86/boot/bzImage is ready  (#59)
> ERROR: "ore_read" [fs/nfs/objlayout/objlayoutdriver.ko] undefined!
> ERROR: "ore_put_io_state" [fs/nfs/objlayout/objlayoutdriver.ko] undefined!
> ERROR: "ore_write" [fs/nfs/objlayout/objlayoutdriver.ko] undefined!
> ERROR: "ore_check_io" [fs/nfs/objlayout/objlayoutdriver.ko] undefined!
> ERROR: "ore_verify_layout" [fs/nfs/objlayout/objlayoutdriver.ko] undefined!
> ERROR: "ore_get_rw_state" [fs/nfs/objlayout/objlayoutdriver.ko] undefined!
> WARNING: modpost: Found 3 section mismatch(es).
> To see full details build your kernel with:
> 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
> make[1]: *** [__modpost] Error 1
> make: *** [modules] Error 2
> tigran@anahit:~/nfs-2.6>
> 
> 
> config file attached.
> 
> Tigran.

Which tree is this?
Because in Benny's tree there was such a problem. But in Linus 3.2-rc1 it 
should be already fixed.

In some version of Benny's tree it is terminally broken. (No why out)
You'll need a patch. Tell me which tree and I'll make one for you

Sorry
Boaz

           reply	other threads:[~2011-11-09 17:29 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAGue13qr5iq=yhCA5BEzeoX94-ha7y4-fXMxH6C1g0nUia2Ceg@mail.gmail.com>]

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=4EBAB863.1030303@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=tigran.mkrtchyan@desy.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox