From: Marcel Holtmann <marcel@holtmann.org>
To: ALBERT RIBAS GUASCH <albert.ribas@estudiants.urv.es>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] problem on make install
Date: Fri, 05 Mar 2004 12:55:39 +0100 [thread overview]
Message-ID: <1078487739.2762.60.camel@pegasus> (raw)
In-Reply-To: <13c0fd76e.d76e13c0f@estudiants.urv.es>
Hi Albert,
> I'm working in a Red Hat with kernel 2.4.18, so I've
> downloaded bluez-kernel-2.3 , untared it, and
> ./configure. Until there there is no problem, but
> when I do make, I need to comment line 461 on core.c
> to skip the error:
the bluez-kernel-2.3 package is deprecated and no longer supported. Use
a vanilla kernel and apply my patch.
> core.c: In function `bnep_session':
> core.c:461: structure has no member named `nice'
> make[2]: *** [core.o] Error 1
> make[1]: *** [bnep.o] Error 2
>
> when I comment that line there is no problem on
> doing the 'make', but on make install I get the next
> messages:
>
> make[1]: Leaving directory
> `/root/testings/bluez-kernel-2.3/doc'
> /sbin/depmod -a
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.18-4custom/kernel/drivers/bluetooth/bluecard_cs.o
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.18-4custom/kernel/drivers/bluetooth/bt3c_cs.o
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.18-4custom/kernel/drivers/bluetooth/btuart_cs.o
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.18-4custom/kernel/drivers/bluetooth/dtl1_cs.o
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.18-4custom/kernel/drivers/bluetooth/hci_uart.o
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.18-4custom/kernel/drivers/bluetooth/hci_usb.o
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.18-4custom/kernel/drivers/bluetooth/hci_vhci.o
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.18-4custom/kernel/misc/ksock_multi.o
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.18-4custom/kernel/misc/ksock_single.o
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.18-4custom/kernel/net/bluetooth/bluez.o
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.18-4custom/kernel/net/bluetooth/bnep.o
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.18-4custom/kernel/net/bluetooth/l2cap.o
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.18-4custom/kernel/net/bluetooth/rfcomm.o
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.18-4custom/kernel/net/bluetooth/sco.o
> make: *** [install] Error 1
>
> can anybody help me on this? I'm new on BlueZ so
> please be gentle!! ;)
I can't give you any assistance here, because you use a custom kernel
and a deprecated package.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2004-03-05 11:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 9:54 [Bluez-users] problem on make install ALBERT RIBAS GUASCH
2004-03-05 11:55 ` Marcel Holtmann [this message]
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=1078487739.2762.60.camel@pegasus \
--to=marcel@holtmann.org \
--cc=albert.ribas@estudiants.urv.es \
--cc=bluez-users@lists.sourceforge.net \
/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