Message354556
| Author |
pablogsal |
| Recipients |
christian.heimes, pablogsal, pitrou, vstinner |
| Date |
2019年10月12日.23:07:53 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<1570921674.08.0.325931849761.issue38282@roundup.psfhosted.org> |
| In-reply-to |
| Content |
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. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2019年10月12日 23:07:54 | pablogsal | set | recipients:
+ pablogsal, pitrou, vstinner, christian.heimes |
| 2019年10月12日 23:07:54 | pablogsal | set | messageid: <1570921674.08.0.325931849761.issue38282@roundup.psfhosted.org> |
| 2019年10月12日 23:07:54 | pablogsal | link | issue38282 messages |
| 2019年10月12日 23:07:53 | pablogsal | create |
|