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
This is an incorrect conversion from wchar_t to char that results in the patch incorrectly returning only the first character (which happens to be the drive letter).
Installed packages
N/A
Environment info
N/A
The text was updated successfully, but these errors were encountered:
Thanks for the report. Could you open a PR that fixes it, or suggest how the implementation should look like? If you have a package/feedstock that exercises this code path, we could also add it as a downstream test here in some form.
The "fix" I applied in that patch was to call GetModuleFileNameA. That seemed appropriate in that library since it didn't really look like any of the downstream code would correctly handle wchar paths anyway, but that may not be an appropriate fix for the STL.
I'm also not sure of the context in which libstdc++ is used on win32 in conda-forge?
I'm also not sure of the context in which libstdc++ is used on win32 in conda-forge?
We just introduced tzdb support (#142), and also the mingw-stack is pretty new (libstcxx is not our default C++ stdlib on windows; in fact, it's not ABI-compatible with the STL, so we have to be very careful to use it).
That said, if it's just renaming the function, then that's a very easy fix; you can even rename it directly in the patch (+ increment the build number).
Solution to issue cannot be found in the documentation.
Issue
The tzinfo patch (https://github.com/conda-forge/ctng-compilers-feedstock/blob/main/recipe/patches/0003-patch-zoneinfo_dir_override-to-point-to-our-tzdata.patch) calls
GetModuleFileNameW
and memcpy's the result into achar*
.This is an incorrect conversion from wchar_t to char that results in the patch incorrectly returning only the first character (which happens to be the drive letter).
Installed packages
Environment info
The text was updated successfully, but these errors were encountered: