----- Original Message ----- From: "Teun Burgers" <[EMAIL PROTECTED]> > 1) How about making libpthread.a a dummy library with just one .o file > with a dummy (empty) function? This does fix this particular > configure problem, but might have side effects since the pthread > symbols > are no longer in libpthread.a
You already know the correct fix to this scenario. Patch ld to be able to act like gcc with -mno-cygwin. Please don't go look for solutions that are really just workarounds. > 2) include the pthread symbols in both libcygwin.a and libpthread.a? I will not support cygwin pthread functions linked statically. I should have said that before. Those functions both depend on cygwin and are depended on by cygwin. > Robert Collins wrote: > > > Hmm. Why not put the win32 api checks in the configure script ahead of > > pthread? > > What do you mean with that? Fix the configure script so that it checks for Win32 availability - and thus win32 thread functions - before pthreads. Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
