From: "Ozan Çağlayan" <ozan@pardus.org.tr>
To: linux-bluetooth@vger.kernel.org
Cc: marcel@holtmann.org
Subject: Re: Undefined symbols in netlink plugin
Date: Mon, 12 Oct 2009 09:48:53 +0300 [thread overview]
Message-ID: <4AD2D155.8040008@pardus.org.tr> (raw)
In-Reply-To: <4AB94E32.8060703@pardus.org.tr>
Ozan Çağlayan wrote On 23-09-2009 01:22:
> Hi,
>
> I'm getting the following when I launch bluetoothd with -n -d:
>
> ..
> Can't load plugin /usr/lib/bluetooth/plugins/netlink.so:
> /usr/lib/bluetooth/plugins/netlink.so: undefined symbol: debug
> ..
>
> AFAIK, those libtool plugins are allowed to have undefined symbols after
> linking as they will probably be resolved during runtime loading but the
> warning above wasn't present on previous versions like 4.41 for example.
>
> # ldd -u -r /usr/lib/bluetooth/plugins/netlink.so
> 26771: /usr/lib/bluetooth/plugins/netlink.so: error: symbol
> lookup error: undefined symbol: g_io_channel_unix_new (continued)
> undefined symbol: g_io_channel_unix_new
> (/usr/lib/bluetooth/plugins/netlink.so)
> 26771: /usr/lib/bluetooth/plugins/netlink.so: error: symbol
> lookup error: undefined symbol: debug (continued)
> undefined symbol: debug (/usr/lib/bluetooth/plugins/netlink.so)
> 26771: /usr/lib/bluetooth/plugins/netlink.so: error: symbol
> lookup error: undefined symbol: g_io_add_watch (continued)
> undefined symbol: g_io_add_watch
> (/usr/lib/bluetooth/plugins/netlink.so)
> 26771: /usr/lib/bluetooth/plugins/netlink.so: error: symbol
> lookup error: undefined symbol: info (continued)
> undefined symbol: info (/usr/lib/bluetooth/plugins/netlink.so)
> 26771: /usr/lib/bluetooth/plugins/netlink.so: error: symbol
> lookup error: undefined symbol: g_io_channel_unref (continued)
> undefined symbol: g_io_channel_unref
> (/usr/lib/bluetooth/plugins/netlink.so)
> Unused direct dependencies:
>
>
> So we have 3 undefined symbol from glib and 2 internal symbols from
> logging.c: debug() and info(). There's no difference if I install the
> libtool la file or not. Since glib is already needed by bluez daemon,
> those undefined symbols seems harmless but AFAIK the internal ones
> should have been linked against the static logging.o.
>
> Or do I miss something?
>
>
> Thanks,
> Ozan Caglayan
>
>
Still an issue on bluez 4.56. CC'ing Marcel Holtmann.
next prev parent reply other threads:[~2009-10-12 6:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-22 22:22 Undefined symbols in netlink plugin Ozan Çağlayan
2009-10-12 6:48 ` Ozan Çağlayan [this message]
2009-10-12 8:37 ` alok barsode
2009-10-13 7:48 ` Ozan Çağlayan
2009-10-13 10:23 ` alok barsode
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=4AD2D155.8040008@pardus.org.tr \
--to=ozan@pardus.org.tr \
--cc=linux-bluetooth@vger.kernel.org \
--cc=marcel@holtmann.org \
/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.