https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90835
--- Comment #3 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> --- > --- Comment #2 from Iain Sandoe <iains at gcc dot gnu.org> --- > does the existing availability hack work [below]? It won't: one major problem was the use of __OSX_AVAILABLE and __OSX_AVAILABLE_STARTING throughout OS headers, but without a fallback definition in <Availability.h> if the compiler used doesn't support __has_builtin and the availability attribute. > * for the other things, if it's a beta, then perhaps there's some chance it > will be fixed before issue. Right: I believe I got at least one such bug fixed during 10.14 Beta. > * we > - unconditionally define __has_xxxxxx(x) 0 in Darwin's builtin defines That's most likely the easiest way out. > - make more fix include hacks.. While possible, it has all the known problems: fixed headers get out of sync with newer headers from Xcode updates or fixes won't longer apply because the select patterns don't match any longer. > - implement __has_xxxxx() .. which would be nicer, but not sure who has time > to do it .. Exactly: I suspect there are more pressing issues with the macOS port than this one ;-)
