You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On Windows, if there are non-ASCII character in the path to LLVM--for example, if someone's name is non-English--then the function will not return the correct result. The function does not error, it just returns malformed UTF-8. However, this results in packages like LLVM.jl refusing to compile if the returned string is malformed UTF-8.
The text was updated successfully, but these errors were encountered:
…acters in path on Windows (#45126) (#45127)
* Fix jl_get_libllvm_impl to support non-ASCII characters
* Fix jl_get_libllvm_impl to support non-ASCII characters, fix whitespace
* Fix jl_get_libllvm_impl to support non-ASCII characters, fix null and buffer
…acters in path on Windows (#45126) (#45127)
* Fix jl_get_libllvm_impl to support non-ASCII characters
* Fix jl_get_libllvm_impl to support non-ASCII characters, fix whitespace
* Fix jl_get_libllvm_impl to support non-ASCII characters, fix null and buffer
(cherry picked from commit 6976bac)
On Windows, if there are non-ASCII character in the path to LLVM--for example, if someone's name is non-English--then the function will not return the correct result. The function does not error, it just returns malformed UTF-8. However, this results in packages like LLVM.jl refusing to compile if the returned string is malformed UTF-8.
The text was updated successfully, but these errors were encountered: