Seriously? !!!
Come on guys, this makes the compiler unusable.
...but as long as you're making a toy compiler, would you consider making one
that does not support pthreads and so avoids this problem?
Thanks.
Hi! Sorry for the interruption, but you may want to take at least a few seconds
to look into some recent license changes for the software you're about to
install.
Parts of the "winpthreads" library will be compiled into every binary file (EXE
or DLL) you create. It's a necessary evil that is currently required in order to
provide support for threads and concurrency in programs compiled by GCC.
The license for winpthreads requires you to reproduce its text in every copy or
substantial portion of the winpthreads library that you distribute. This means
that even if you just want to distribute a single small executable, created with
TDM-GCC (or any winpthreads-based GCC release), you must include a copy of that
license.
Check the license out in the file "COPYING.winpthreads.txt", which will be
installed along with TDM-GCC. Consult with a lawyer if you have any concerns
about how you can use this software.
Does this new license hurt your usage of GCC? Let the developers know!
File a feature request asking them to change the winpthreads license or get rid
of GCC's winpthreads requirement, at:
https://sourceforge.net/p/mingw-w64/feature-requests/new/
Send an email to the MinGW-w64 mailing list, at:
mingw-w64-public@lists.sourceforge.net
------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
