<html>
<head>
<base href="https://bugs.llvm.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - "version" include wreaks havoc on case-insensitive filesystems"
href="https://bugs.llvm.org/show_bug.cgi?id=42540">42540</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>"version" include wreaks havoc on case-insensitive filesystems
</td>
</tr>
<tr>
<th>Product</th>
<td>libc++
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P
</td>
</tr>
<tr>
<th>Component</th>
<td>All Bugs
</td>
</tr>
<tr>
<th>Assignee</th>
<td>unassignedclangbugs@nondot.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>quentin@mit.edu
</td>
</tr>
<tr>
<th>CC</th>
<td>llvm-bugs@lists.llvm.org, mclow.lists@gmail.com
</td>
</tr></table>
<p>
<div>
<pre>- 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?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>