60
edits
Hamzaalloush (talk | contribs) |
|||
Line 183: | Line 183: | ||
== porting to GCC 5.1 == | == porting to GCC 5.1 == | ||
well, there has been some progress to the missing exports for libstdc++, one of GCC's main developers has started arranging a patch after few other reporting with successful attemps freezing of the missing functions to an older version. a few other issues have arrisen after more investigation for this bug, so should we port back to GCC 5.1 when the patch is complete? is it worth it? https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66030 -- [[User:Hamzaalloush|Hamzaalloush]] ([[User talk:Hamzaalloush|talk]]) 20:21, 3 June 2015 (EDT) | well, there has been some progress to the missing exports for libstdc++, one of GCC's main developers has started arranging a patch after few other reporting with successful attemps freezing of the missing functions to an older version. a few other issues have arrisen after more investigation for this bug, so should we port back to GCC 5.1 when the patch is complete? is it worth it? https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66030 -- [[User:Hamzaalloush|Hamzaalloush]] ([[User talk:Hamzaalloush|talk]]) 20:21, 3 June 2015 (EDT) | ||
: MXE has committed a [https://github.com/mxe/mxe/commit/6947d3245f9c76d9124a4c4f3c164154a75f3f62 patch] to fix building with GCC 5. I haven't tested it yet, though. Currently, I'm working on upstreaming the changes here (slowly), so that we can then work on the main upstream branch (with GCC 5 compatibility). -- [[User:Flyhigh|Flyhigh]] ([[User talk:Flyhigh|talk]]) 22:35, 4 June 2015 (EDT) |
edits