public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: A Guy Called Tyketto <tyketto@wizard.com>
To: linux-kernel@vger.kernel.org
Subject: virt_to_bus_not_defined_use_pci_map: Missed a couple
Date: Wed, 20 Feb 2002 23:10:51 -0800	[thread overview]
Message-ID: <20020221071051.GA17927@wizard.com> (raw)


        Just had these go bung while giving 2.5.5 a compile:

make[1]: Leaving directory `/usr/src/linux-2.5.5/arch/i386/mm'
make -C  arch/i386/lib modules_install
make[1]: Entering directory `/usr/src/linux-2.5.5/arch/i386/lib'
make[1]: Nothing to be done for `modules_install'.
make[1]: Leaving directory `/usr/src/linux-2.5.5/arch/i386/lib'
cd /lib/modules/2.5.5; \
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  2.5.5; fi
depmod: *** Unresolved symbols in /lib/modules/2.5.5/kernel/drivers/net/de4x5.o
depmod:         virt_to_bus_not_defined_use_pci_map
depmod: *** Unresolved symbols in /lib/modules/2.5.5/kernel/sound/oss/sound.o
depmod:         virt_to_bus_not_defined_use_pci_map
make: *** [_modinst_post] Error 1

        Luckily I'm not going to be using these for the moment, so my kernel 
is good to go, but thought I'd give you a heads up.

                                                        BL.
-- 
Brad Littlejohn                         | Email:        tyketto@wizard.com
Unix Systems Administrator,             |           tyketto@ozemail.com.au
Web + NewsMaster, BOFH.. Smeghead! :)   |   http://www.wizard.com/~tyketto
  PGP: 1024D/E319F0BF 6980 AAD6 7329 E9E6 D569  F620 C819 199A E319 F0BF


                 reply	other threads:[~2002-02-21  7:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20020221071051.GA17927@wizard.com \
    --to=tyketto@wizard.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