https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89864
--- Comment #12 from Iain Sandoe <iains at gcc dot gnu.org> --- (In reply to Jürgen Reuter from comment #11) > (In reply to Iain Sandoe from comment #10) > > > In the short-term, I'd suggest picking up the previous version of Xcode > > command line tools [e.g.10.1] (from developer.apple.com) and using the SDK > > from that? While this gets fixed. > > with "while this gets fixed" you mean waiting for an update from the Apple > side (like an XCode 10.2.1 update or so),\ Yes. > or a 'proper' fix from the gcc side? Well, this doesn't seem to be a GCC bug - but if someone can propose a work-around, that's fine (I just have doubts that a fix includes will be enough). > And if it is a fix from the Apple side, how will I know that an update > contains the desired fix? We will only be able to figure that out by testing it - of course, if you file a radar about it - then presumably that would be updated when it's fixed.
