-
-
Notifications
You must be signed in to change notification settings - Fork 520
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Case insensitivity strikes again ("failed to move output file" while building Python on Mac) #1144
Comments
Hey! I'm not a maintainer of this repo, but I was able to run this command no problem on Debian Linux. My filesystems is also case-insensitive. |
How is your file system case insensitive on Linux? Usually Linux is case sensitive, in which case the command would succeed. |
Ugh you're right, sorry about that. Please ignore my comment. My ingrish is failing me. |
I suppose in that case the Windows build should also fail: https://learn.microsoft.com/en-us/windows/wsl/case-sensitivity |
So I think the binary needs to go somewhere else, or be called something else. I suggest, as a really lame cop-out, naming it |
When we removed the com suffix from ape binaries, we broke the build for ape's python for any case-insensitive file system, i.e. Windows and XNU, because there is a third_party/python/Python that gets mirrored in the o directory with the python object files and clashes with the binary name. This patch hacks around this by renaming the binary to "python3" so that it no longer clashes with that directory.
The symptom is this:
The cause seems to be that there is a
o/aarch64/third_party/python/Python
directory, and Mac filesystems are usually case-insensitive.The text was updated successfully, but these errors were encountered: