This makes it obvious that libc++ is used in an unsupported configuration, and the compiler probably has to be updated. It often happens that people try to use libc++ and don't realize that their compiler is too old.
- Group Reviewers
- rG2b7f11a6523b: [libc++] Warn if an unsupported compiler is used
Note the patch is a bit premature. Until LLVM-17 is released we still support LLVM-15.
@emaste Once LLVM 17 is released libc++ will drop support for Clang 15. Can you update the FreeBSD CI to Clang 16 or Clang 17. If you prefer to do the update after the LLVM 17 release can you let us know?
Once LLVM 17 is released libc++ will drop support for Clang 15. Can you update the FreeBSD CI to Clang 16 or Clang 17
Updating to Clang 16 now makes sense, and I'll plan to do it next week.
(Clang 16 is what we use in the FreeBSD base system as well.)
I'll update to 17 a little after it is released.
Then we should have a separate PR to do that. I had it on my todo list for after the release, but I'm not objecting to do it a week before the release. Especially since I'm not aware of patches we want to backport to the release branch. Once that patch has landed this one can be rebased.