From: Dick <dm@chello.nl>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] inline problem gcc 3.4.2 and 2.6.9-mh3
Date: Sat, 6 Nov 2004 13:28:04 +0100 [thread overview]
Message-ID: <200411061328.04823.dm@chello.nl> (raw)
Hi,
GCC 3.4.2 doesn't seem like the prototypes:
static inline u8 l2cap_get_ident(struct l2cap_conn *conn);
static inline int l2cap_send_req(struct l2cap_conn *conn, u8 ident, u8 code,
u16 len, void *data);
output:
# make
<snip>
net/bluetooth/l2cap.c: In function `__l2cap_sock_close':
net/bluetooth/l2cap.c:77: sorry, unimplemented: inlining failed in call to
'l2cap_get_ident': function body not available
net/bluetooth/l2cap.c:284: sorry, unimplemented: called from here
net/bluetooth/l2cap.c:78: sorry, unimplemented: inlining failed in call to
'l2cap_send_req': function body not available
net/bluetooth/l2cap.c:291: sorry, unimplemented: called from here
When I remove inline it seems to compile:
net/bluetooth/l2cap.c:77: warning: 'l2cap_get_ident' declared inline after
being called
net/bluetooth/l2cap.c:77: warning: previous declaration of 'l2cap_get_ident'
was here
net/bluetooth/l2cap.c:78: warning: 'l2cap_send_req' declared inline after
beingcalled
net/bluetooth/l2cap.c:78: warning: previous declaration of 'l2cap_send_req'
washere
Could someone please take a look at this?
Thanks in advance,
Dick
-------------------------------------------------------
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/listinfo/bluez-devel
next reply other threads:[~2004-11-06 12:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-06 12:28 Dick [this message]
2004-11-06 13:17 ` [Bluez-devel] inline problem gcc 3.4.2 and 2.6.9-mh3 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=200411061328.04823.dm@chello.nl \
--to=dm@chello.nl \
--cc=bluez-devel@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 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.