public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: Misbehaviour with "make foo.ko"
Date: Thu, 17 Feb 2011 23:31:56 +0100	[thread overview]
Message-ID: <4D5DA1DC.4040902@suse.cz> (raw)
In-Reply-To: <20110217164945.1cf0b31e@lxorguk.ukuu.org.uk>

On 17.2.2011 17:49, Alan Cox wrote:
> Trying to rebuild single modules gets into a mess
> 
> [alan@pyx linux-psbdev]$ make drivers/staging/mrst/pvr/psb_gfx.ko
>   CHK     include/linux/version.h
>   CHK     include/generated/utsrelease.h
>   CALL    scripts/checksyscalls.sh
>   CC [M]  drivers/staging/mrst/pvr/../drv/psb_fb.o
>   CC [M]  drivers/staging/mrst/pvr/../drv/psb_intel_lvds.o
>   LD [M]  drivers/staging/mrst/pvr/psb_gfx.o
>   MODPOST 1 modules
> ERROR: "ttm_object_device_release" [drivers/staging/mrst/pvr/psb_gfx.ko]
> undefined!
> ERROR ...

It works fine here with 2.6.38-rc5 and ext3.ko:

$ touch fs/ext3/namei.c
$ make O=/dev/shm/build fs/ext3/ext3.ko
  Using /labs/mmarek/linux-2.6 as source for kernel
  GEN     /dev/shm/build/Makefile
  CHK     include/linux/version.h
  CHK     include/generated/utsrelease.h
  CALL    /labs/mmarek/linux-2.6/scripts/checksyscalls.sh
  CC [M]  fs/ext3/namei.o
  LD [M]  fs/ext3/ext3.o
  MODPOST 3065 modules
WARNING: modpost: Found 56 section mismatch(es).
To see full details build your kernel with:
'make CONFIG_DEBUG_SECTION_MISMATCH=y'
  LD [M]  fs/ext3/ext3.ko
$

Where do I find the psb_gfx driver? I don't see it in linux-next.

Michal

      reply	other threads:[~2011-02-17 22:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-17 16:49 Misbehaviour with "make foo.ko" Alan Cox
2011-02-17 22:31 ` Michal Marek [this message]

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=4D5DA1DC.4040902@suse.cz \
    --to=mmarek@suse.cz \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kbuild@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