From: reg@dwf.com
To: linux-kernel@vger.kernel.org
Subject: Test6: still an error in 'make install'
Date: Sun, 28 Sep 2003 22:55:31 -0600 [thread overview]
Message-ID: <200309290455.h8T4tVdd006356@orion.dwf.com> (raw)
Here is the log file for the end of my build and install of -test6
---
...
BUILD arch/i386/boot/bzImage
Root device is (3, 7)
Boot sector 512 bytes.
Setup is 2544 bytes.
System is 1845 kB
Kernel: arch/i386/boot/bzImage is ready
[root@orion linux-2.6.0-test6]# make modules
make[1]: `arch/i386/kernel/asm-offsets.s' is up to date.
Building modules, stage 2.
MODPOST
[root@orion linux-2.6.0-test6]# make modules_install
Warning: you may need to install module-init-tools
See http://www.codemonkey.org.uk/post-halloween-2.5.txt
INSTALL fs/binfmt_aout.ko
INSTALL drivers/net/dummy.ko
INSTALL drivers/base/firmware_class.ko
if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.6.0-test6; fi
[root@orion linux-2.6.0-test6]# make install
make[1]: `arch/i386/kernel/asm-offsets.s' is up to date.
CHK include/linux/compile.h
Kernel: arch/i386/boot/bzImage is ready
sh /usr/src/linux-2.6.0-test6/arch/i386/boot/install.sh 2.6.0-test6
arch/i386/boot/bzImage System.map ""
No module aic7xxx found for kernel 2.6.0-test6
mkinitrd failed
make[1]: *** [install] Error 1
make: *** [install] Error 2
[root@orion linux-2.6.0-test6]#
---
note that the compile and build of the kernel finish with NO errors.
note that there are NO modules in this build.
Then note that there is some some silly error about:
No module aic7xxx found for kernel 2.6.0-test6
during the 'make install' that causes the install to fail.
I have been seeing this error ever since -test1.
Has anyone tracked this thing down???
--
Reg.Clemens
reg@dwf.com
next reply other threads:[~2003-09-29 4:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 4:55 reg [this message]
2003-09-29 8:04 ` Gawain Lynch
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=200309290455.h8T4tVdd006356@orion.dwf.com \
--to=reg@dwf.com \
--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®