https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82824
--- Comment #3 from Eric Gallager <egallager at gcc dot gnu.org> --- (In reply to r...@cebitec.uni-bielefeld.de from comment #2) > > --- Comment #1 from Eric Gallager <egallager at gcc dot gnu.org> --- > [...] > > Apparently 10.6/Darwin 11 isn't supported either; see bug 82829. As I said > > I couldn't find an explicit statement of support (or non-support) for > LLVM on Darwin. However, we could either try to get patches upstream > or keep them gcc-local if they are as trivial as those two. > > > there, it'd really be nice to have a --disable-libsanitizer configure flag > > for whenever upstream breaks stuff again > > Your wish has already been granted: for most if not all target > libraries, there's already a --disable-libX/--enable-libX switch, > libsanitizer included. Really? It doesn't show up in the ./configure --help output: Local-Admins-MacBook-Pro:gcc ericgallager$ ./configure --help=recursive | grep -i sanit Report bugs to <libsanitizer>. Local-Admins-MacBook-Pro:gcc ericgallager$ > > However, this isn't the right way to handle this: if it's really > concluded that libsanitizer isn't supported on certain Darwin versions, > this should be handled in libsanitizer/configure.tgt so users don't get > failing bootstraps without non-default options. > > Rainer
