[ARM] wvdial seems unusable on armel due to reliance on the unimplemented sysv ucontext API in glibc

[Dave Martin]

To work around this, wvstreams should be ported to use another mechanism such as setjmp/longjmp (I haven't investigated the feasibility of this), or the affected functions (primarily setcontext and getcontext) need to be implemented in glibc.

The affected code is in utils/wvtask.cc. I don't think the functions are used anywhere else.

See also https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/383975.

[Paul Larson (pwlars)]

I'm combining this with bug #383975 since they describe the same problem and it seems that either ucontext should be implemented, or a workaround, but probably not both.

[David Sugar (dyfet-deactivatedaccount)]

It is worth noting that this problem seems entirely confined to utils/wvtask.cc. One key difference to note about ucontext vs set/longjmp is that signal states are also saved in the context_t. I think this could be patched adding a new configure --disable-ucontext option and some arch tests in the debian/rules to add it to configure until glibc is patched, assuming suitable working setjmp/longjmp based replacement code is added to wvtask.cc.