Hi Chris, On Tue, 2015-07-21 at 13:47 +0300, Alexey Brodkin wrote:
Hi,
When building Boost for ARC architecture we're seeing this failure: --------------------->8--------------------- ./boost/asio/detail/impl/eventfd_select_interrupter.ipp: In member function 'void boost::asio::detail::eventfd_select_interrupter::open_descriptors()': ./boost/asio/detail/impl/eventfd_select_interrupter.ipp:50:50: error: '__NR_eventfd' was not declared in this scope write_descriptor_ = read_descriptor_ = syscall(__NR_eventfd, 0); --------------------->8---------------------
This happens clearly because ARC following Linux kernel's UAPI doesn't define __NR_eventfd syscall.
If you look here https://github.com/torvalds/linux/blob/master/include/uapi/asm-generic/unist... you may notice that "eventfd" syscall with some others resides in "#ifdef__ARCH_WANT_SYSCALL_NO_FLAGS".
And from what I may see only "score" architecture has this __ARCH_WANT_SYSCALL_NO_FLAGS defined.
Most of other arches that don't use unistd.h from "include/uapi/asm-genereic" folder have "eventfd" syscall defined. For example it's true for ARM (both 32 and 64 versions).
So I'd say it's not the best way to use directly a syscall that's being obsoleted in "Boost". And so real fix would be to modify Boost's "eventfd_select_interrupter::open_descriptors()" for example with use of really generic "eventfd2" or even better use libc's eventfd() call instead of direct syscall.
Any thoughts what would be the best fix here?
Looks like this message was never approved by mailing list admin and so was not published. Could you please take a look at this issue? And a little bit more context - for ARC we only have uClibc-based toolchain and it sets: --------------->8----------------- #define __GLIBC__ 2 #define __GLIBC_MINOR__ 2 --------------->8----------------- see http://git.uclibc.org/uClibc/tree/include/features.h#n395 I'm wondering what could be the right solution for that problem? -Alexey