summaryrefslogtreecommitdiff
path: root/FAQ
diff options
context:
space:
mode:
authorrpj <rpj>1999-03-11 15:06:20 +0000
committerrpj <rpj>1999-03-11 15:06:20 +0000
commitb14e60afab45a7bc5eff231f408505a1bec6b436 (patch)
tree4f9980eea7b03957476af05736a2c8364027d9c3 /FAQ
parent52f7c3f5ef6d9b70ec385fb390bf27962e68ee3d (diff)
Thu Mar 11 09:01:48 1999 Ross Johnson <rpj@ixobrychus.canberra.edu.au>
* pthread.h (pthread_mutex_t): revert to (pthread_mutex_t *); define a value to serve as PTHREAD_MUTEX_INITIALIZER. (pthread_mutex_t_): remove staticinit and valid elements. (pthread_cond_t): revert to (pthread_cond_t_ *); define a value to serve as PTHREAD_COND_INITIALIZER. (pthread_cond_t_): remove staticinit and valid elements. * mutex.c (pthread_mutex_t args): adjust indirection of references. (all functions): check for PTHREAD_MUTEX_INITIALIZER value; check for NULL (invalid). * condvar.c (pthread_cond_t args): adjust indirection of references. (all functions): check for PTHREAD_COND_INITIALIZER value; check for NULL (invalid). Wed Mar 10 17:18:12 1999 Ross Johnson <rpj@ixobrychus.canberra.edu.au> * misc.c (CancelableWait): Undo changes from Mar 8 and 7. tests/ChangeLog Fri Mar 12 08:34:15 1999 Ross Johnson <rpj@ixobrychus.canberra.edu.au> * eyal1.c (main): Fix trylock loop; was not waiting for thread to lock the "started" mutex.
Diffstat (limited to 'FAQ')
-rw-r--r--FAQ14
1 files changed, 8 insertions, 6 deletions
diff --git a/FAQ b/FAQ
index da9cd75..71e6359 100644
--- a/FAQ
+++ b/FAQ
@@ -5,22 +5,24 @@
INDEX
-----
-Q 1 How do I get pthreads-win32 to link under Cygwin or Mingw32?
+Q 1 Should I use Cygwin or Mingw32 as a development environment?
Q 2 Now that pthreads-win32 builds under Mingw32, why do I get
memory access violations?
=============================================================================
-Q 1 How do I get pthreads-win32 to link under Cygwin or Mingw32?
+Q 1 Should I use Cygwin or Mingw32 as a development environment?
---
A 1
---
-The following email from Anders Norlander explains how to solve this
-problem. I think the proviso is that the DLL and your application should
-both be built with the same development environment (cygwin, mingw,
-or MSVC etc).
+Important: see Q2 also.
+
+I short, use Mingw32 with the MSVCRT library to build applications that use
+the DLL. You cannot build the library itself with either yet because the
+library uses C++ EH which is not thread-safe in egcs yet. Use MSVC or grab
+the pre-build DLL etc.
Date: Mon, 07 Dec 1998 15:11:37 +0100
From: Anders Norlander <anorland@hem2.passagen.se>