From: Ben Collins <bcollins@debian.org>
To: "Richard B. Johnson" <root@chaos.analogic.com>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Firewire on Linux-2.4.20
Date: Tue, 11 Mar 2003 15:44:29 -0500 [thread overview]
Message-ID: <20030311204429.GD379@phunnypharm.org> (raw)
In-Reply-To: <Pine.LNX.3.95.1030311152746.8672A-100000@chaos>
> # cd drivers/ieee*
> # ls *.o
> csr.o hosts.o ieee1394_core.o nodemgr.o pcilynx.o sbp2.o
> highlevel.o ieee1394.o ieee1394_transactions.o ohci1394.o raw1394.o
> # ls -la pcilynx.o
> -rw-r--r-- 1 root root 16432 Mar 11 15:30 pcilynx.o
> # depmod pcilynx.o
> depmod: *** Unresolved symbols in pcilynx.o
> pcilynx.o:
> pcilynx.o: unresolved symbol i2c_transfer
> pcilynx.o: unresolved symbol i2c_bit_del_bus
> pcilynx.o: unresolved symbol i2c_bit_add_bus
Everything built fine this time. Redo "make modules" with the SUBDIRS
option to get the rest built.
I strongly believe this is something local to your system. Maybe your
system clock is wrong and it is confusing make. Maybe you don't have all
the right tools installed. I'm not realy sure, but I do know it is not a
problem in ieee1394 itself.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo - http://www.deqo.com/
next prev parent reply other threads:[~2003-03-11 20:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 19:29 Firewire on Linux-2.4.20 Richard B. Johnson
2003-03-11 20:03 ` Ben Collins
2003-03-11 20:39 ` Richard B. Johnson
2003-03-11 20:44 ` Ben Collins [this message]
2003-03-11 21:08 ` Richard B. Johnson
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=20030311204429.GD379@phunnypharm.org \
--to=bcollins@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.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 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.