One of the commits for Makefile.am has

winpthreads doesn't depend on libpthread.  We only needed it because
gcc was trying to link it by default.  This is most likely a gcc bug.
andoni on irc found a workaround.  The frontend has a -no-pthread
switch to prevent this default linking.  winpthreads now uses that to
link, and we can thusly remove the fake libpthread from the build
entirely.

On 8 May 2015 at 14:25, LRN <[email protected]> wrote:
> On 08.05.2015 8:13, Luke Allardyce wrote:
>> When building winpthreads as part of a cross compiler I found that the
>> dll won't compile as the -no-pthread flag isn't passed to gcc
>>
>
> I remember something about giving gcc a fake pthread library to allow earlier
> stage to be built. Can't say anything definitive right now, as i don't have
> access to my gcc-building machine.
>
> --
> O< ascii ribbon - stop html email! - www.asciiribbon.org
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> _______________________________________________
> Mingw-w64-public mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>

------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to