https://bugs.llvm.org/show_bug.cgi?id=42540
Bug ID: 42540
Summary: "version" include wreaks havoc on case-insensitive
filesystems
Product: libc++
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: normal
Priority: P
Component: All Bugs
Assignee: unassignedclangb...@nondot.org
Reporter: quen...@mit.edu
CC: llvm-bugs@lists.llvm.org, mclow.li...@gmail.com
- libc++ >= 7.0 has an include file called `version` (as part of C++20)
- Many open source packages contain a file called `VERSION` (this is a standard
file in autoconf-based distributions)
- On a case-insensitive filesystem, #include <version> finds `VERSION` and
hilarity ensues.
I'm really not sure what the best fix would be. Asking thousands of open-source
projects to rename their `VERSION` files seems like a huge challenge. Asking
clang to be case-sensitive even when the underlying filesystem is not seems
like a non-starter. libc++ could at least not having any includes of <version>
within the standard library itself, but that just postpones the pain until it
starts being included in other libraries.
Is it too late to raise this as a standards issue?
--
You are receiving this mail because:
You are on the CC list for the bug._______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs
