Re: boost-libs build failure on amd64-9.99.17

["John D. Baker" <jdbaker%consolidated.net@localhost>]

My original message seems to have run afoul of a SPAM filter or some such.
Replying to it to see if that passes:

On Sat, 19 Oct 2019, John D. Baker wrote:

> Date: Sat, 19 Oct 2019 21:35:41 -0500 (CDT)
> From: John D. Baker <jdbaker%skuld.technoskunk.fur@localhost>
> To: pkgsrc-users%NetBSD.org@localhost
> Subject: boost-libs build failure on amd64-9.99.17
> 
> Building devel/boost-libs on NetBSD/amd64-9.99.17 fails with:
> 
> [...]
> gcc.compile.c++ bin.v2/libs/log/build/gcc-7.4.0/release/link-static/threadapi-pthread/threading-multi/visibility-hidden/syslog_backend.o
> In file included from /usr/include/stddef.h:37:0,
>                  from /usr/include/g++/cstddef:50,
>                  from ./boost/config/compiler/gcc.hpp:165,
>                  from ./boost/config.hpp:39,
>                  from ./boost/log/detail/config.hpp:34,
>                  from libs/log/src/syslog_backend.cpp:18:
> ./boost/asio/detail/impl/kqueue_reactor.ipp: In constructor 'boost::asio::detail::kqueue_reactor::kqueue_reactor(boost::asio::execution_context&)':
> ./boost/asio/detail/impl/kqueue_reactor.ipp:32:5: error: invalid static_cast from type 'intptr_t {aka long int}' to type 'void*'
>      EV_SET(ev, ident, filt, flags, fflags, data, \
>      ^
> [...]
> 
> in several places.
> 
> I seem to recall something about the EV_SET() macro being changed at some
> point.  I noticed a patch for "security/sudo" that provides an alternate
> EV_SET() macro definition for NetBSD versions before 9.99.14.
> 
> Is something like that at play here?

-- 
|/"\ John D. Baker, KN5UKS               NetBSD     Darwin/MacOS X
|\ / jdbaker[snail]consolidated[flyspeck]net  OpenBSD            FreeBSD
| X  No HTML/proprietary data in email.   BSD just sits there and works!
|/ \ GPGkeyID:  D703 4A7E 479F 63F8 D3F4  BD99 9572 8F23 E4AD 1645