* Linker error with pthreads-w32-2-6-0-release
@ 2006-08-01 10:03 Nigel Horne
2006-08-03 12:25 ` EnterCriticalSection (&ptw32_cond_list_lock) on pthreads-w32-2-6-0-release Nigel Horne
0 siblings, 1 reply; 2+ messages in thread
From: Nigel Horne @ 2006-08-01 10:03 UTC (permalink / raw)
To: pthreads-win32
When I attempt to link with pthreads I get:
(pthread.obj) : error LNK2019: unresolved external symbol _WSASetLastError@4
referenced in function _pthread_once
(pthread.obj) : error LNK2019: unresolved external symbol _WSAGetLastError@0
referenced in function _pthread_once
Perhaps pthread_once() is wrong about the calling convention for
WSAGet/SetLastError, and is using cdecl by mistake?
--
Nigel Horne. Adjudicator, Arranger, Band Trainer, Composer, Typesetter.
NJH Music, Barnsley, UK. ICQ#20252325. Skype: nigelhorne
njh@bandsman.co.uk http://www.bandsman.co.uk
^ permalink raw reply [flat|nested] 2+ messages in thread
* EnterCriticalSection (&ptw32_cond_list_lock) on pthreads-w32-2-6-0-release
2006-08-01 10:03 Linker error with pthreads-w32-2-6-0-release Nigel Horne
@ 2006-08-03 12:25 ` Nigel Horne
0 siblings, 0 replies; 2+ messages in thread
From: Nigel Horne @ 2006-08-03 12:25 UTC (permalink / raw)
To: pthreads-win32
What are the circumstances under which VS2005 gives an
access violation whenever
EnterCriticalSection(&ptw32_cond_list_lock);
is called in any of the pthread functions?
Since ptw32_cond_list_lock is an internal variable, I can't
see that I supposed to initialise it, yet nothing works
because of this EnterCriticalSection problem, e.g.
pthread_cond_init
will fail.
-Nigel
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-08-03 12:25 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-08-01 10:03 Linker error with pthreads-w32-2-6-0-release Nigel Horne
2006-08-03 12:25 ` EnterCriticalSection (&ptw32_cond_list_lock) on pthreads-w32-2-6-0-release Nigel Horne
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).