This is the mail archive of the cygwin-apps mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On 4/9/2013 06:17, JonY wrote: > On 4/9/2013 03:58, Charles Wilson wrote: > >> >> Yes. I'm not sure how that should be handled. If you want to "force" the >> switch, for that particular toolchain, then the cygwin package of the >> mingw-w64-headers for that toolchain should probably stop shipping those >> files, so that the (new) winpthreads package for that toolchain can >> start shipping them. >> >> If you DON'T want to force the switch, then...? Use the alternatives >> framework for those particular headers? >> > > > Good point, I'll simply remove the headers on my next header/CRT refresh > if I ship winpthreads. It's not something that can be switched easily as > it changes the underlying libgomp ABI, requiring GCC to be recompiled to > work with pthreads-win32. > Uploaded mingw64-x86_64-winpthreads-3.0b_svn5726-1, along with mingw64-x86_64-gcc-4.8-20130310-2. The new GCC is a rebuild of the -1, with dependency on winpthreads. I plan to make a new mingw-w64-headers/crt release in the near future and fix the conflicts. For now, these will suffice. New mingw-w64-headers/crt for 32bit cygwin next weekend, and maybe for the 64bit cygwin too if I get enough time.
Attachment:
signature.asc
Description: OpenPGP digital signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |