[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [bluetooth-dev] Unresolved symbol when using insmod bt.o (Stack: 0_0_5 & Kernel: 2.4.2)
> -----Original Message-----
> From: Supriyo Chatterjea [mailto:firstname.lastname@example.org]
> Sent: 16 July 2001 11:21
> To: email@example.com
> Subject: [bluetooth-dev] Unresolved symbol when using insmod bt.o
> (Stack: 0_0_5 & Kernel: 2.4.2)
> I have compiled the Axis stack successfully. However, when I
> try to execute insmod bt.o, I get the following error messages:
> bt.o: unresolved symbol hci_receive_acl
> bt.o: unresolved symbol hci_receive_bcsp
> bt.o: unresolved symbol hci_receive_event
> bt.o: unresolved symbol csr_waitcmdnum
> bt.o: unresolved symbol hci_receive_hq
> bt.o: unresolved symbol bt_write_lower_driver_real
> I'm using Axis stack 0_0_5, kernel version 2.4.2 and RedHat 6.2,
> gcc version: egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
> I don't face any problems however, if I use Axis stack
> 20010530 together with kernel version 2.2.19.
> Any clues as to what might be causing this problem? I tried
> using kernel 2.4.6 but ended up getting the same results as
> 2.4.2. I've seen similar postings ont his mailing list...
> but didn't find any suitable answers.
> Thanks in advance!
The problem is actually that the BCSP source files are compiled
and linked into the bt.o module, even if BCSP support is not
wanted. This has been fixed in the CVS repository, where you
should now use 'make INCLUDE_BCSP_SUPPORT=1' to build with
support for BCSP.
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to firstname.lastname@example.org