[Vm-dev] Re: Issue 132 in cog: Build Fails on OpenBSD. ucontext
is not available
Eliot Miranda
eliot.miranda at gmail.com
Wed Oct 9 21:04:25 UTC 2013
On Wed, Oct 9, 2013 at 12:42 AM, <cog at googlecode.com> wrote:
>
>
> Comment #2 on issue 132 by riverdu... at gmail.com: Build Fails on OpenBSD.
> ucontext is not available
> http://code.google.com/p/cog/**issues/detail?id=132<http://code.google.com/p/cog/issues/detail?id=132>
>
> Hi
>
>
> Hang on. I don't think that's the problem. I *think* someone found out
>> how to install a ucontext.h for FreeBSD. Is that the case?
>>
>
> That isn't the point.
> Firstly we're talking OPENBSD, not FREEBSD which is vastly different.
> 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.
I'm happy to make the change. But I could do with some help. BTW, I'm not
using any functions here. Only the u_context accessing via the siginfo
parameter passed into a signal handler as in
void (*__sa_sigaction)(int, struct __siginfo *, void *);
So if you know how to get the register state from that on OpenBSD I'd like
to know. Otherwise condescend to someone else, ok?
>
>
> (meant to post this yesterday; the draft has sat there, but it's still a
>> valid question)
>>
>
> Best
> Dusty
>
>
> --
> You received this message because this project is configured to send all
> issue notifications to this address.
> You may adjust your notification preferences at:
> https://code.google.com/**hosting/settings<https://code.google.com/hosting/settings>
>
--
best,
Eliot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/vm-dev/attachments/20131009/795e30bc/attachment-0001.htm
More information about the Vm-dev
mailing list