On Sun, Aug 5, 2012 at 1:09 PM, JonY <[email protected]> wrote: > On 8/5/2012 16:59, niXman wrote: >> 2012/8/5 Ruben Van Boxem: >> >>> This might be it. I build and install libgcc before the rest of gcc. I added >>> this step to resolve some link error I encountered once, and left it in to >>> be sure it never happened again. >> >> In other words, it turns out that there were made some changes in >> trunk that need libgcc to be built separately? >> > > Actually, I just succeeded in getting around that error, > x86_64-w64-mingw32-gcc 4.8.0 is working fine here. > > Remove the --enable-sjlj-exceptions part from your configure, don't > disable it either. --enable-sjlj-exceptions still makes win64 target use > sjlj, though there is a bug in libgcc that confuses this, causing the error.
Can you write a PR? ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
