Ion Gaztañaga wrote:

El 19/12/2025 a las 21:07, David McFarland via Boost escribió:

...

Hi,

I've created a set of patches that together allow boost to build on cygwin.

- https://github.com/boostorg/asio/pull/463 - https://github.com/boostorg/context/pull/322 - https://github.com/boostorg/process/pull/533 - https://github.com/boostorg/stacktrace/pull/219 - https://github.com/boostorg/system/pull/137

I also made a tracking issue with links to all of them:

- https://github.com/boostorg/boost/issues/1112

Being cygwin a POSIX emulation layer, I'm curious why the patch directs Asio to use the win32 API. Maybe the cygwin POSIX-like API is not complete enough for Asio's needs?

The patch seems to me to do the exact opposite; direct Asio to use POSIX.

Yeah, sorry. I interpreted the other way. Sorry for the noise! Ion ________________________________ From: David McFarland <corngood@gmail.com> Sent: Monday, December 22, 2025 5:21:23 PM To: Ion Gaztañaga <igaztanaga@gmail.com> Cc: Boost developers' mailing list <boost@lists.boost.org> Subject: Re: Cygwin patches

Being cygwin a POSIX emulation layer, I'm curious why the patch directs Asio to use the win32 API. Maybe the cygwin POSIX-like API is not complete enough for Asio's needs?

The patch should be disabling the win32 stuff on cygwin for almost everything, so that it falls back to the POSIX implementation. Like: -#if defined(BOOST_ASIO_WINDOWS) || defined(__CYGWIN__) +#if defined(BOOST_ASIO_WINDOWS)