In ptw32_InterlockedCompareExchange.c, I've added a section forBorland's compiler; it's identical to that for the MS compiler exceptthat it uses /* ... */ comments instead of ; comments.[RPJ: need to define HAVE_TASM32 in config.h to use the above.]The other file is a makefile suitable for use with Borland's compiler(run "make -fBmakefile" in the directory).  It builds a single versionof the library, pthreadBC.dll and the corresponding pthreadBC.libimport library, which is comparable to the pthreadVC version; I can'tpersonally see any demand for the versions that include structured orC++ exception cancellation handling so I haven't attempted to buildthose versions of the library.  (I imagine a static version might beof use to some, but we can't legally use that on my commercialprojects so I can't try that out, unfortunately.)[RPJ: Added tests\Bmakefile as well.]Borland C++ doesn't define the ENOSYS constant used by pthreads-win32;rather than make more extensive patches to the pthreads-win32 source Ihave a mostly-arbitrary constant for it in the makefile.  However thisdoesn't make it visible to the application using the library, so ifanyone actually wants to use this constant in their apps (why?)someone might like to make a seperate NEED_BCC_something define to addthis stuff.The makefile also #defines EDEADLK as EDEADLOCK, _timeb as timeb, and_ftime as ftime, to deal with the minor differences between the twoRTLs' naming conventions, and sets the compiler flags as required toget a normal compile of the library.[RPJ: Moved errno values and _timeb etc to pthread.h, so apps will alsouse them.](While I'm on the subject, the reason Borland users should recompilethe library, rather than using the impdef/implib technique suggestedpreviously on the mailing list, is that a) the errno constants aredifferent, so the results returned by the pthread_* functions can bemeaningless, and b) the errno variable/pseudo-variable itself isdifferent in the MS & BCC runtimes, so you can't access thepthreadVC's errno from a Borland C++-compiled host applicationcorrectly - I imagine there are other potential problems from the RTLmismatch too.)[RPJ: Make sure you use the same RTL in both dll and application builds.The dll and tests Bmakefiles use cw32mti.lib. Having some trouble withmemory read exceptions running the test suite using BCC55.]Best regards,Will-- Will BryantSystems Architect, eCOSM LimitedCell +64 21 655 443, office +64 3 365 4176http://www.ecosm.com/