From: Frank Davis <fdavis112@juno.com>
To: linux-kernel@vger.kernel.org
Cc: Dax Kelson <dax@gurulabs.com>, fdavis112@juno.com
Subject: Re: test12-pre3 (FireWire issue)
Date: Fri, 1 Dec 2000 01:59:15 -0500 (EST) [thread overview]
Message-ID: <391350194.975653957785.JavaMail.root@web425-wra> (raw)
Dax,
What is your modutils version? Is this the first test12 that has caused this error?
Regards,
Frank
> Linus, Andreas,
>
> I've been using this same config since FireWire was merged, just tried out
> test12-pre3 and got an unresolved symbol problem with raw1394.o
>
> #
> # IEEE 1394 (FireWire) support
> #
> CONFIG_IEEE1394=y
> # CONFIG_IEEE1394_PCILYNX is not set
> CONFIG_IEEE1394_OHCI1394=y
> CONFIG_IEEE1394_VIDEO1394=m
> CONFIG_IEEE1394_RAWIO=m
> # CONFIG_IEEE1394_VERBOSEDEBUG is not set
>
>
> make bzImage; make modules; make modules_install
>
> modules_install bombs out with:
>
> cd /lib/modules/2.4.0-test12; \
> 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.4.0-test12; fi depmod: *** Unresolved symbols in
> /lib/modules/2.4.0-test12/kernel/drivers/ieee1394/raw1394.o
> depmod: free_tlabel
> depmod: fill_iso_packet
> depmod: hpsb_register_highlevel
> depmod: highlevel_lock
> depmod: hpsb_unregister_highlevel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-01 7:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-01 6:59 Frank Davis [this message]
2000-12-01 7:03 ` test12-pre3 (FireWire issue) Dax Kelson
-- strict thread matches above, loose matches on Subject: below --
2000-11-29 6:57 test12-pre3 Linus Torvalds
2000-12-01 6:00 ` test12-pre3 (FireWire issue) Dax Kelson
2000-12-04 0:10 ` Andreas Bombe
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=391350194.975653957785.JavaMail.root@web425-wra \
--to=fdavis112@juno.com \
--cc=dax@gurulabs.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