This makes it seem like it has several options instead of ucontext, and
even wants to define CORO_ASM on OpenBSD:
['OS == "linux" or OS == "solaris" or OS == "sunos" or OS == "freebsd"',
{'defines': ['CORO_UCONTEXT']}],
['OS == "mac"', {'defines': ['CORO_SJLJ']}],
['OS == "openbsd"', {'defines': ['CORO_ASM']}],
...
g++ '-D_LARGEFILE_SOURCE' '-D_FILE_OFFSET_BITS=64' '-DUSE_CORO'
'-DCORO_GUARDPAGES=1' '-DCORO_UCONTEXT' '-DBUILDING_NODE_EXTENSION'
^^^^^^^^^^^^^^^^
But this shows that it isn't detecting OpenBSD correctly. Maybe ask the
author why that would be?
On Tue, Nov 05, 2013 at 01:14:00PM +0000, openda...@hushmail.com wrote:
> Hello,
>
> On 5. november 2013 at 1:06 PM, "David Coppa" <dco...@gmail.com> wrote:
> >
> >OpenBSD lacks the ucontext.h and associated functions
> >(setcontext/getcontext, swapcontext, and makecontext).
>
> Ouch. That does not look good. From
> https://code.google.com/p/cog/issues/detail?id=132 --
>
> > Secondly, its not about "can i get this to work with my favorite distro".
> > ucontext is a long deprecated library that makes use of long deprecated c
> > functions. Using it goes against best practices.
> > If it weren't for certain applications/distros, ucontext would be dead a
> > long time ago.
> > The idea is to replace the deprecated library with something that doesn't
> > use deprecated c functions and is more portable.
>
> Any idea what to do?
>
> Thanks.
>
> O.D.
