From: Dale Amon <amon@vnl.com>
To: linux-kernel@vger.kernel.org
Subject: make install bug?
Date: Sat, 6 Apr 2002 16:15:31 +0100 [thread overview]
Message-ID: <20020406151531.GK17144@vnl.com> (raw)
When building kernels for my servers I have always done this:
make INSTALL_MOD_PATH=/usr/src/<target-hostname> modules_install
to dump all the modules into an easily tarballable directory
to be scp'd to the target host.
However for some reason today it's tried to do a depmod on the
kernel building machine:
make -C arch/i386/lib modules_install
make[1]: Entering directory `/VNetLinux/linux-2.4.18/arch/i386/lib'
make[1]: Nothing to be done for `modules_install'.
make[1]: Leaving directory `/VNetLinux/linux-2.4.18/arch/i386/lib'
cd /VNetLinux/scout/lib/modules/2.4.18; \
mkdir -p pcmcia; \
find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia
if [ -r System.map ]; then /sbin/depmod -ae -F System.map -b /VNetLinux/scout -r 2.4.18; fi
depmod: *** Unresolved symbols in /VNetLinux/scout/lib/modules/2.4.18/pcmcia/3c575_cb.o
depmod: pcibios_read_config_byte
depmod: pcibios_write_config_word
depmod: pcibios_read_config_dword
depmod: pcibios_write_config_byte
depmod: pcibios_write_config_dword
depmod: pcibios_read_config_word
depmod: *** Unresolved symbols in /VNetLinux/scout/lib/modules/2.4.18/pcmcia/aha152x_cs.o
depmod: print_msg
depmod: scsi_command_size
depmod: scsi_unregister_module
depmod: scsicam_bios_param
And so forth....
I'm not sure why this started happening, but it isn't nice
behavior at all. I'd call it a bug as I can't imagine why
I'd want a depmod to occur on the build machine.
Have I managed to tickle something that should not be
happening?
next reply other threads:[~2002-04-06 15:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-06 15:15 Dale Amon [this message]
2002-04-06 15:34 ` make install bug? Dale Amon
2002-04-06 15:50 ` Keith Owens
-- strict thread matches above, loose matches on Subject: below --
2005-12-12 15:35 eschvoca
2005-12-12 17:54 ` Junio C Hamano
2005-12-16 15:06 ` eschvoca
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=20020406151531.GK17144@vnl.com \
--to=amon@vnl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.