From: Marcel Holtmann <marcel@holtmann.org>
To: David Krapohl <david.krapohl@halifax.rwth-aachen.de>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] l2cap.c fails on compile
Date: Sun, 31 Oct 2004 10:42:36 +0100 [thread overview]
Message-ID: <1099215756.16247.33.camel@pegasus> (raw)
In-Reply-To: <200410311038.10680.david.krapohl@halifax.rwth-aachen.de>
Hi David,
> Can anybody confirm, that the latest bluetooth patch fails on compile?
> I get this error message with patch-2.6.9-mh3 and vanilla-sources:
>=20
> CC [M] net/bluetooth/l2cap.o
> net/bluetooth/l2cap.c: In function `__l2cap_sock_close':
> net/bluetooth/l2cap.c:77: nicht implementiert: =BBinline=AB beim Aufruf=
von=20
> =BBl2cap_get_ident=AB gescheitert: function body not available
> net/bluetooth/l2cap.c:284: nicht implementiert: von hier aufgerufen
> net/bluetooth/l2cap.c:78: nicht implementiert: =BBinline=AB beim Aufruf=
von=20
> =BBl2cap_send_req=AB gescheitert: function body not available
> net/bluetooth/l2cap.c:291: nicht implementiert: von hier aufgerufen
> make[2]: *** [net/bluetooth/l2cap.o] Fehler 1
> make[1]: *** [net/bluetooth] Fehler 2
> make: *** [net] Fehler 2
what compiler do you used?
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-10-31 9:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-31 9:38 [Bluez-devel] l2cap.c fails on compile David Krapohl
2004-10-31 9:42 ` Marcel Holtmann [this message]
2004-10-31 10:27 ` David Krapohl
2004-10-31 10:45 ` Marcel Holtmann
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=1099215756.16247.33.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=david.krapohl@halifax.rwth-aachen.de \
/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.