-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
gcc/ld doesn't support unicode paths #17812
Comments
Unicode version gcc&binutils Unless it's |
Looks like an issue between UTF-16 (wide strings) and UTF-8; with the former being the encoding of choice on Windows it's reinterpreting the heart as two UTF-8 surrogate pairs instead of a single UTF-16 pair. I wonder if that's fixable at all, especially considering how GNU thinks about |
+1 |
On MSYS2 and Cygwin the binary gets built, but running it generates a segfault:
Midipix on the other hand goes without a crash:
But the exit code is non-zero. |
Looking through their website, midipix does a lot of work to make sure the extra steps in UTF-16LE conversions work as they should; I wonder if artifacts compiled on their toolchain have the same conversions linked in though |
The package may help a little: https://packages.msys2.org/base/mingw-w64-unicode-character-database However, it still has some issues. For example when I do such things: gcc 测试.c -o 测试 As expected there should be a 测试.exe in the folder if compiled successfully. However, even if compiled successfully, there is only one file named There are other issues no matter whether the beta UNICODE support on Windows is enabled or not. Perhaps that is really an issue with encoding but not Unicode support. |
Description / Steps to reproduce the issue
Expected behavior
Should produce an object/executable.
Actual behavior
Fails with error.
Verification
Windows Version
MINGW64_NT-10.0-19045
MINGW environments affected
Are you willing to submit a PR?
No response
The text was updated successfully, but these errors were encountered: