From: Sam Ravnborg <sam@ravnborg.org>
To: Bill Davidsen <davidsen@tmr.com>,
Kai Germaschewski <kai@tp1.ruhr-uni-bochum.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [2.5.63] aha152x, module issues
Date: Tue, 4 Mar 2003 21:43:28 +0100 [thread overview]
Message-ID: <20030304204328.GA7271@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0303031710370.22041-100000@oddball.prodigy.com>
On Mon, Mar 03, 2003 at 05:11:10PM -0500, Bill Davidsen wrote:
> scripts/Makefile.modinst:16: *** Uh-oh, you have stale module entries. You messed with SUBDIRS, do not complain if something goes wrong.
This happens if you have encountered a compile error in a module.
In this case you did not succeed the compilation of fs/binfmt_aout,
and therefore no .o file can be located.
kbuild assumes this is because you have messed with SUBDIRS, which is wrong.
Kai - the following patch fixes this for me.
Sam
===== scripts/Makefile.build 1.31 vs edited =====
--- 1.31/scripts/Makefile.build Wed Feb 19 23:42:13 2003
+++ edited/scripts/Makefile.build Tue Mar 4 21:40:47 2003
@@ -163,12 +163,12 @@
# Single-part modules are special since we need to mark them in $(MODVERDIR)
$(single-used-m): %.o: %.c FORCE
- $(touch-module)
ifdef CONFIG_MODVERSIONS
$(call if_changed_rule,vcc_o_c)
else
$(call if_changed_dep,cc_o_c)
endif
+ $(touch-module)
quiet_cmd_cc_lst_c = MKLST $@
cmd_cc_lst_c = $(CC) $(c_flags) -g -c -o $*.o $< && \
@@ -262,8 +262,8 @@
$(call if_changed,link_multi-y)
$(multi-used-m) : %.o: $(multi-objs-m) FORCE
- $(touch-module)
$(call if_changed,link_multi-m)
+ $(touch-module)
targets += $(multi-used-y) $(multi-used-m)
next prev parent reply other threads:[~2003-03-04 20:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 22:11 Bill Davidsen
2003-03-04 20:43 ` Sam Ravnborg [this message]
2003-03-04 21:28 ` Kai Germaschewski
2003-03-04 22:43 ` Bill Davidsen
2003-03-05 5:42 ` Sam Ravnborg
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=20030304204328.GA7271@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=davidsen@tmr.com \
--cc=kai@tp1.ruhr-uni-bochum.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
all inboxes | Powered by JetHome®