It's not posix per-se, it's "posix threads" (of which there is a win32 port available in mingw). This is done sometimes to ease porting of software from posix to windows.
An update: Kevin submitted a patch to use win32 threads for Rtools (restoring the previous behavior) and Duncan is rebuilding Rtools now with this change. Once we have this update in hand we can test again. On Thu, Mar 12, 2015 at 7:13 PM, Avraham Adler <avraham.ad...@gmail.com> wrote: > Why would posix be enabled for a Windows target? > > Avi > > On Thu, Mar 12, 2015 at 6:49 PM, Duncan Murdoch <murdoch.dun...@gmail.com> > wrote: >> >> On 12/03/2015 5:51 PM, Jeroen Ooms wrote: >> > On Thu, Mar 12, 2015 at 2:40 PM, JJ Allaire <jj.alla...@gmail.com >> > <mailto:jj.alla...@gmail.com>> wrote: >> > >> > I had an issue like this in RcppParallel that was solved by >> > rebuilding >> > Rcpp from source using the very latest R-devel and Rtools 3.3. Have >> > you tried that? >> > >> > >> > Yes, that doesn't seem to help. >> > >> > I have a suspicion now. I have seen this behavior before when linking >> > libraries on windows that were built with different threading models. >> > Based on gcc -v, the old rtools (and hence my v8 static libs) use win32 >> > threading, whereas the new rtools has been built with >> > --enable-threads=posix. >> >> The scripts are on CRAN, if you want to try modifying them. However, if >> the scripts aren't satisfactory very soon, I'll just go back to the >> previous Rtools. >> >> Duncan >> >> _______________________________________________ >> Rcpp-devel mailing list >> Rcpp-devel@lists.r-forge.r-project.org >> https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel > > _______________________________________________ Rcpp-devel mailing list Rcpp-devel@lists.r-forge.r-project.org https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel
