Please see the provided link for a detailed analysis of the problem. Unfortunately the provided patch did not suffice to solve the problem for me, so I updated it by including a proper isystem include path which worked fine. The attached patch is basically the patch from upstream with that modification. As a nice side effect, one sed call can be removed from the ebuild. Reproducible: Always
Created attachment 296855 [details, diff] upstream fix for win32api include path (with modification for isystem include path) Fix from upstream w/ isystem include path added by myself. - adds new configure option for win32api include path - adds isystem include path to necessary places
Created attachment 296857 [details, diff] diff from original ebuild
*** Bug 395937 has been marked as a duplicate of this bug. ***
it is failing, but i think i'll de-KEYWORD it until upstream can sort it out
(In reply to comment #4) > it is failing, but i think i'll de-KEYWORD it until upstream can sort it out Any news on the patch? sys-devel/crossdev-20120305 selects this version, despite it having no keywords...
(In reply to comment #5) > (In reply to comment #4) > > it is failing, but i think i'll de-KEYWORD it until upstream can sort it out > sys-devel/crossdev-20120305 selects this version, > despite it having no keywords... n/m about crossdev, that was my fault. Anyway, it'd still be interesting to know what upstream decided to do about the ldbl issue.
should be all set now in the tree; thanks for the report! Commit message: Add patch to fix LDBL_MIN_EXP build failures http://sources.gentoo.org/dev-util/mingw-runtime/files/mingw-runtime-3.20-LDBL_MIN_EXP.patch?rev=1.1 http://sources.gentoo.org/dev-util/mingw-runtime/mingw-runtime-3.20.ebuild?r1=1.2&r2=1.3
What about to unmask this package?
