[debian-hurd-Patches][312155] pth 2.0.7
Patches item #312155, was changed at 13/12/2009 00:20 by Samuel Thibault
You can respond by visiting:
https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=312155&group_id=30628
>Status: Closed
Priority: 3
Submitted By: Pino Toscano (pino-guest)
Assigned to: Nobody (None)
Summary: pth 2.0.7
Category: None
Group: None
>Resolution: Fixed
Initial Comment:
Current pth (2.0.7-14) fails to build because of incomplete porting for the setting of the context jmpbuf.
Although, pth 2.0.7-12 built, and the reason seems like older glibc provided the JB_* macros for the jmpbuf "slots" ([1] for example).
The attached "solution" has been taken from the i386 part of [1], ie defining back JB_* macros if needed.
As a result, pth now compiles and seem to be working, so the sanity check in gpgme's configure should not fail.
[1] http://www.mail-archive.com/user-mode-linux-devel@lists.sourceforge.net/msg02974.html
----------------------------------------------------------------------
>Comment By: Samuel Thibault (sthibault)
Date: 09/04/2011 15:46
Message:
Fixed nowadays.
----------------------------------------------------------------------
Comment By: Samuel Thibault (sthibault)
Date: 13/12/2009 15:37
Message:
Maybe the short-term solution could be to just upload a pth with your
patch on debian-ports?
----------------------------------------------------------------------
Comment By: Pino Toscano (pino-guest)
Date: 13/12/2009 15:32
Message:
I agree, and in fact the configure (see configure.ac) has a workaround to not use the sigaltstack implementation on Hurd, even if found.
Otherwise, the other short-term solution would be disabling the pth sanity check in gpgme, as the current pth is detected to be unusable.
----------------------------------------------------------------------
Comment By: Samuel Thibault (sthibault)
Date: 13/12/2009 12:31
Message:
Mmm, not really pretty indeed. The long-term solution is rather to fix
sigaltstack, which should be as soon as glibc stops using the stack for
thread-specific data.
----------------------------------------------------------------------
You can respond by visiting:
https://alioth.debian.org/tracker/?func=detail&atid=410472&aid=312155&group_id=30628
Reply to: