Closed revelator closed 3 years ago
I'm missing some context here, what version of what file in what package is this happening in?
Nevermind, spotted it in lib\gcc\x86_64-w64-mingw32\9.2.0\include\float.h
.
exactly ;) the guard gets circumvented by the unguarded include. Not sure how to go about fixing it in the build chain or if its even nessesary anymore ?.
This looks to be fixed in the upcoming TDM-GCC 10.3.0 release.
Welcome back m8 :)
The mingw32-float.h.patch gets circumvented by changes to gcc's build chain which now uses a sed script to do allmost the same as your patch, so we end up with two #include_next.
One from your patch and another unguarded one from the sed script.
`#if defined (MINGW32) && ! defined (_MINGW_FLOATH) /* MinGW.org's runtime libraries provide a supplementary float.h, which
include_next
endif
endif / _FLOAT_H___ /
include_next`