From: Sam Ravnborg <sam@ravnborg.org>
To: Dave Jones <davej@redhat.com>, walt <wa1ter@myrealbox.com>,
linux-kernel@vger.kernel.org
Subject: Re: [2.6.5-bk] 'modules_install' failed to install modules
Date: Wed, 14 Apr 2004 22:25:54 +0200 [thread overview]
Message-ID: <20040414202554.GA12020@mars.ravnborg.org> (raw)
In-Reply-To: <20040414170010.GA23419@redhat.com>
On Wed, Apr 14, 2004 at 06:00:10PM +0100, Dave Jones wrote:
>
> Make this the third. I just saw it happen here too.
> 'make bzImage ; make modules ; make modules_install' fails in the above way.
> Doing a 'make' seems to work.
I think I tracked it down now.
During 'make bzImage' the directory .tmp_versions was deleted and created.
This is only supposed to happen when building modules.
This does not match your failure report 100%.
I assume what you did was something like:
make bzImage
make modules
make install <= This would trigger the above case
make modules_install
Or maybe you inverted the two:
make modules
make bzImage
Anyway here is the fix.
Please let me know if you still se problems.
Sam
===== Makefile 1.478 vs edited =====
--- 1.478/Makefile Tue Apr 13 17:46:49 2004
+++ edited/Makefile Wed Apr 14 22:19:26 2004
@@ -624,8 +624,10 @@
endif
prepare0: prepare1 include/linux/version.h include/asm include/config/MARKER
+ifneq ($(KBUILD_MODULES),)
$(Q)rm -rf $(MODVERDIR)
- $(if $(CONFIG_MODULES),$(Q)mkdir -p $(MODVERDIR))
+ $(Q)mkdir -p $(MODVERDIR)
+endif
# All the preparing..
prepare-all: prepare0 prepare
next prev parent reply other threads:[~2004-04-14 20:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-14 15:40 walt
2004-04-14 16:18 ` Sam Ravnborg
2004-04-14 16:43 ` Gene Heskett
2004-04-14 17:00 ` Dave Jones
2004-04-14 19:10 ` Gene Heskett
2004-04-14 20:25 ` Sam Ravnborg [this message]
2004-04-14 20:42 ` Dave Jones
2004-04-15 5:12 ` Simon Fowler
2004-04-15 14:55 ` Sam Ravnborg
2004-04-15 4:47 ` Simon Fowler
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=20040414202554.GA12020@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wa1ter@myrealbox.com \
/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®