mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Andi Kleen <ak@suse.de>
Cc: linux-kernel@vger.kernel.org, agruen@suse.de
Subject: Re: Building external modules against objdirs
Date: Sun, 30 Jul 2006 19:51:30 +0200	[thread overview]
Message-ID: <20060730175130.GA23665@mars.ravnborg.org> (raw)
In-Reply-To: <200607301846.07797.ak@suse.de>

On Sun, Jul 30, 2006 at 06:46:07PM +0200, Andi Kleen wrote:
> 
> Hi,
> 
> It looks like building external modules against separate objdirs doesn't work 
> anymore in 2.6.18.
I just tried it out with -linus (from a few hours ago).
$> cd ~/kernel/linux-2.6
$> mkdir ../o
$> make O=../o defconfig
$> make O=../o
...
$> cd ~/kernel/external
$> cat Makefile
obj-m := sam.o
sam-y := sam1.o
EXTRA_CFLAGS := -I$(src)/include

$> make M=`pwd` O=~/kernel/o -C ~/kernel/linux-2.6
make: Entering directory `/home/sam/kernel/linux-2.6'
  LD      /home/sam/kernel/external/built-in.o
  CC [M]  /home/sam/kernel/external/sam1.o
  LD [M]  /home/sam/kernel/external/sam.o
  Building modules, stage 2.
  MODPOST
  CC      /home/sam/kernel/external/sam.mod.o
  LD [M]  /home/sam/kernel/external/sam.ko
make: Leaving directory `/home/sam/kernel/linux-2.6'

So it seems to work out fine here.

Can you check that you really did a 'make prepare' in the relevant
output directory. Previously only the make *config step was needed.

	Sam

  reply	other threads:[~2006-07-30 17:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-30 16:46 Andi Kleen
2006-07-30 17:51 ` Sam Ravnborg [this message]
2006-07-30 17:49   ` Andi Kleen
2006-07-30 18:31     ` Sam Ravnborg
2006-07-30 18:37       ` Andi Kleen
2006-07-30 19:17         ` Sam Ravnborg
2006-07-30 20:06           ` Andi Kleen
2006-07-31  9:39           ` Roman Zippel
2006-08-01 19:42             ` Sam Ravnborg
2006-07-30 18:34     ` Sam Ravnborg
2006-07-30 18:42       ` Andi Kleen

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=20060730175130.GA23665@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=agruen@suse.de \
    --cc=ak@suse.de \
    --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

Powered by JetHome