[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+T2pCHL=zqFG_08SYkOJe2Lw1dyBtzmZDmbffkbNsWCeNxG_g@mail.gmail.com>
Date: Mon, 29 Jan 2018 09:38:00 -0600
From: William Pitcock <nenolod@...eferenced.org>
To: musl@...ts.openwall.com
Subject: Re: getcontext, setcontext, makecontext and swapcontext
Hi,
On Sun, Jan 28, 2018 at 6:24 AM, Tmp File <tmpfile@...l.com> wrote:
> Hello all.
>
> I'm compiling many software in a musl box and (by far) the biggest wall I hit regards the functions getcontext, setcontext, makecontext and swapcontext. I understand they are deprecated, but they are used in many programs and it's usually really troublesome/tricky to modify the upstream source code to accomodate for them being unavailable on musl.
>
> David du Colombier from plan9port mentioned[0] a simple coroutine library called libstak[1] that should help.
> I see 2 possible approaches:
> (i) musl imports libstak
> (ii} users somehow compile libstak and make it available for programs that need the *context functions
>
> In case you aren't interested in (i) could somebody help us get (ii) to work?
> Then musl distros like Alpine could have libstak as some kind of "compatibility" layer.
> Of course (i) might be a better solution, if you aren't so concerned about getcontext, setcontext, makecontext and swapcontext "deprecation status".
Unfortunately, libtask does not actually contain/provide getcontext()
or setcontext(). It only provides makecontext() and swapcontext().
Implementing a library that has these functions is on my todo list.
William
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
