From: Sam Ravnborg <sam@ravnborg.org>
To: Jochen Hein <jochen@jochen.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [2.5.53, KBUILD] missing dependencies for yenta_socket.ko?
Date: Sat, 28 Dec 2002 20:56:37 +0100 [thread overview]
Message-ID: <20021228195637.GA14787@mars.ravnborg.org> (raw)
In-Reply-To: <87wulucxhw.fsf@gswi1164.jochen.org>
On Sat, Dec 28, 2002 at 10:18:35AM +0100, Jochen Hein wrote:
>
> I changed yenta.c and tried to recompile yenta_socket.ko, the
> resulting kernel module. I get:
>
> root@gswi1164:/usr/src/linux-2.5.53# LANG=C make drivers/pcmcia/yenta_socket.ko
> make: Nothing to be done for `drivers/pcmcia/yenta_socket.ko'.
Above trick does not work for composite objects.
The best approach is to use the following trick:
make SUBDIRS=drivers/pcmcia
That will build all files - as required - starting with drivers/pcmcia.
The rest of the build process then proceeds as opposed to the normal
single targets.
The top-level Makefile needs an entry to let the above work with single
target .ko files, patch attached (on top of my earlier kbuild changes).
Sam
===== Makefile 1.349 vs edited =====
--- 1.349/Makefile Fri Dec 27 21:15:43 2002
+++ edited/Makefile Sat Dec 28 13:13:55 2002
@@ -419,6 +419,8 @@
$(Q)$(MAKE) $(build)=$(@D) $@
%.o: %.c scripts FORCE
$(Q)$(MAKE) $(build)=$(@D) $@
+%.ko: %.c scripts FORCE
+ $(Q)$(MAKE) $(build)=$(@D) KBUILD_BUILTIN=1 KBUILD_MODULES=1 $@
%.lst: %.c scripts FORCE
$(Q)$(MAKE) $(build)=$(@D) $@
%.s: %.S scripts FORCE
prev parent reply other threads:[~2002-12-28 19:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-28 9:18 Jochen Hein
2002-12-28 19:56 ` Sam Ravnborg [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=20021228195637.GA14787@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=jochen@jochen.org \
--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
all inboxes | Powered by JetHome®