[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [bluetooth-dev] suse compile problem, redhat insmod problem
I got a whole lot of unresolved symbols as well - initially. But once I
upgraded to 2.2.19...things started working.
Another thing to look out for: The version of gcc that comes with RedHat 7.1
seems to haveo some problem when compiling 0.0.5. So I went back to good old
RH6.2 and that more or less solved my compilation problems.
As for the symbols hci_receive_acl, hci_receive_bcsp, hci_receive_event,
etc, you need to #undef the bcsp options in btconfig.h. I'm currently using
kernel 2.4.6 together with 0.0.5 and I've managed to carry out compilation
----- Original Message -----
From: "Per Haglund" <email@example.com>
Sent: Wednesday, July 18, 2001 5:43 PM
Subject: [bluetooth-dev] suse compile problem, redhat insmod problem
> Hi everybody,
> I've been unable to get the 0.0.5 version of the stack up and running,
> neither with SuSE or Redhat.
> With Redhat, kernel 2.2.18, I get a long list of unresolved symbols when
> I insmod bt.o, similar to Patrick Clauberg's problem in April: jiffies,
> printk, panic, kmalloc etc. I also have a few other symbols such as
> hci_receive_acl, hci_receive_bcsp, hci_receive_event etc.
> With SuSE, I can't even compile the stack. In the userstack directory
> the linker needs the termcap library and even though I've installed it
> (according to SuSE's YAST), no joy. If anyone has advice on SuSE
> installations, please let me know. Otherwise, I'd be happy just getting
> it to work in Redhat :)
> I'm not a Linux master, so there might be something obviously wrong that
> I'm missing. I've looked through the mailing list archive but have not
> managed to find an answer (that made sense to me).
> Kindest regards,
> Per Haglund
> To unsubscribe from this list: send the line "unsubscribe bluetooth-dev"
> the body of a message to firstname.lastname@example.org
Do You Yahoo!?
Get your free @xxxxxxx.com">http://mail.yahoo.com
To unsubscribe from this list: send the line "unsubscribe bluetooth-dev" in
the body of a message to email@example.com