From: Jim Gifford <maillist@jg555.com>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Build issue current MIPS - RaQ2
Date: Sat, 19 Mar 2005 11:17:09 -0800 [thread overview]
Message-ID: <423C7AB5.2010200@jg555.com> (raw)
I have not been able to build kernels since 2.6.9 on my RaQ2 for some
time. I have tried the linux-mips.org port and the current 2.6.11.5
release. I keep getting the same error.
Building modules, stage 2.
MODPOST
*** Warning: "pci_iounmap" [drivers/net/tulip/tulip.ko] undefined!
*** Warning: "pci_iomap" [drivers/net/tulip/tulip.ko] undefined!
with Make V=1
Building modules, stage 2.
make -rR -f /usr/src/linux-2.6.11.5/scripts/Makefile.modpost
scripts/mod/modpost -o /usr/src/linux-2.6.11.5/Module.symvers
vmlinux drivers/block/loop.o drivers/block/rd.o drivers/cdrom/cdrom.o
drivers/char/rtc.o drivers/net/tulip/tulip.o drivers/scsi/scsi_mod.o
drivers/scsi/scsi_transport_spi.o drivers/scsi/sd_mod.o
drivers/scsi/sr_mod.o drivers/scsi/st.o
drivers/scsi/sym53c8xx_2/sym53c8xx.o fs/exportfs/exportfs.o
fs/isofs/isofs.o fs/lockd/lockd.o fs/nfs/nfs.o fs/nfsd/nfsd.o
fs/nls/nls_ascii.o fs/nls/nls_base.o fs/nls/nls_cp437.o
fs/nls/nls_iso8859-1.o fs/nls/nls_utf8.o fs/smbfs/smbfs.o lib/crc32.o
lib/zlib_inflate/zlib_inflate.o net/key/af_key.o
net/netlink/netlink_dev.o net/packet/af_packet.o net/sunrpc/sunrpc.o
net/unix/unix.o
*** Warning: "pci_iounmap" [drivers/net/tulip/tulip.ko] undefined!
*** Warning: "pci_iomap" [drivers/net/tulip/tulip.ko] undefined!
Now it seems to me that the Makefile.modpost would need to include
arch/mips/lib/iomap.o file to correct this issue, but that doesn't seem
like the correct thing to do, and I have no clue on how to do that.
--
----
Jim Gifford
maillist@jg555.com
next reply other threads:[~2005-03-19 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-19 19:17 Jim Gifford [this message]
2005-03-20 6:27 ` Patch for iomap on MIPS was Re: Build issue current MIPS - RaQ2 Jim Gifford
2005-03-20 6:30 ` Andrew Morton
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=423C7AB5.2010200@jg555.com \
--to=maillist@jg555.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