Pablo Galindo Salgado <pablog...@gmail.com> added the comment:
The failures on FreeBSD are:
/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Modules/socketmodule.c:1931:50:
error: no member named 'bt_l2' in 'union sock_addr'
struct sockaddr_l2 *addr = &addrbuf->bt_l2;
~~~~~~~ ^
/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Modules/socketmodule.c:1950:50:
error: no member named 'bt_rc' in 'union sock_addr'
struct sockaddr_rc *addr = &addrbuf->bt_rc;
~~~~~~~ ^
/usr/home/buildbot/python/3.x.koobs-freebsd10.nondebug/build/Modules/socketmodule.c:1967:51:
error: no member named 'bt_hci' in 'union sock_addr'
struct sockaddr_hci *addr = &addrbuf->bt_hci;
~~~~~~~ ^
3 errors generated.
This is likely due to the fact that those fields are protected by:
typedef union sock_addr {
#ifdef HAVE_BLUETOOTH_BLUETOOTH_H
struct sockaddr_l2 bt_l2;
struct sockaddr_rc bt_rc;
struct sockaddr_sco bt_sco;
struct sockaddr_hci bt_hci;
#elif defined(MS_WINDOWS)
}
and in those machines HAVE_BLUETOOTH_BLUETOOTH_H is absent.
----------
nosy: +pablogsal
_______________________________________
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue38282>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
