Package: asio Version: 1.4.1-3.1 Tags: fixed Hi,
in the mean time, this issue got fixed upstream. See their issue #2683 and subversion rev 50961: "Use a pipe if eventfd is not supported at runtime.". Judging by date, this fix should be included since at least 1.4.0. I've checked and can confirm that it's included in upstream version 1.4.1, which Debian currently ships (except for oldstable). https://svn.boost.org/trac/boost/ticket/2683 https://svn.boost.org/trac/boost/changeset/50961 Note that the fix doesn't change the select_interrupter, but instead teaches eventfd_select_interrupter to fall back using a pipe, in case the eventfd() syscall fails. (Interestingly, in all failure cases, not just ENOSYS.) I do not quite understand the motivation for the second proposal of the OP, but favor delivering the same header files independent of build time (and machine). After all, "requiring all users to test for it" is just a preprocessor-macro. Obviously, the proposed work-around - setting ASIO_DISABLE_EVENTFD - is not needed, anymore. Regards Markus Wanner -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
