---
mingw-w64-headers/include/versionhelpers.h | 79
++
1 file changed, 79 insertions(+)
create mode 100644 mingw-w64-headers/include/versionhelpers.h
diff --git a/mingw-w64-headers/include/versionhelpers.h b/mingw-w64-headers/include/versionhelpers.h
new file mode
---
mingw-w64-headers/include/sdkddkver.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/mingw-w64-headers/include/sdkddkver.h b/mingw-w64-headers/include/sdkddkver.h
index 0433811..1b965ae 100644
--- a/mingw-w64-headers/include/sdkddkver.h
+++ b/mingw-w64-headers/include/sdkddkver.h
@@
Patch is ok.
Thanks,
Kai
PS: In hope we get soon a lot of the upcoming Windows X APIs
2015-03-19 14:49 GMT+01:00 Jacek Caban ja...@codeweavers.com:
---
mingw-w64-headers/include/sdkddkver.h | 3 +++
1 file changed, 3 insertions(+)
Likewise, patch is ok.
Thanks,
Kai
2015-03-19 14:49 GMT+01:00 Jacek Caban ja...@codeweavers.com:
---
mingw-w64-headers/include/versionhelpers.h | 79
++
1 file changed, 79 insertions(+)
create mode 100644 mingw-w64-headers/include/versionhelpers.h
I've noticed some unexpected behaviour with winpthreads which I believe
is a bug. Thread-cancellation cleanup handlers are not called when a
thread terminates due to a call to pthread_exit(). This is unexpected;
the pthread_cleanup_push(), pthread_cleanup_pop() specification [1]
mentions: