Default to without-c-locale-coercion #36
Comments
lazka
added a commit
that referenced
this issue
Apr 22, 2022
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Apr 22, 2022
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Apr 24, 2022
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Apr 25, 2022
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
May 18, 2022
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
naveen521kk
pushed a commit
that referenced
this issue
Jun 7, 2022
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Aug 5, 2022
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Aug 12, 2022
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Aug 12, 2022
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
naveen521kk
pushed a commit
that referenced
this issue
Sep 11, 2022
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
naveen521kk
pushed a commit
that referenced
this issue
Sep 11, 2022
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Oct 15, 2022
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Oct 15, 2022
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Dec 8, 2022
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Dec 9, 2022
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Feb 10, 2023
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Feb 10, 2023
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Apr 7, 2023
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Apr 7, 2023
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Apr 7, 2023
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Jun 12, 2023
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Jun 14, 2023
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
naveen521kk
pushed a commit
that referenced
this issue
Jul 15, 2023
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Jul 19, 2023
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Jul 19, 2023
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Aug 25, 2023
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Aug 27, 2023
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Oct 2, 2023
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Oct 2, 2023
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Dec 6, 2023
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Dec 7, 2023
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Feb 10, 2024
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Feb 12, 2024
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Apr 11, 2024
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Apr 12, 2024
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
brainos233
pushed a commit
to brainos233/cpython-mingw
that referenced
this issue
Apr 17, 2024
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes msys2-contrib#36
naveen521kk
pushed a commit
that referenced
this issue
Aug 5, 2024
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
naveen521kk
pushed a commit
that referenced
this issue
Sep 9, 2024
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Sep 10, 2024
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Sep 10, 2024
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
naveen521kk
pushed a commit
that referenced
this issue
Nov 2, 2024
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Dec 22, 2024
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Dec 23, 2024
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Dec 23, 2024
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Feb 5, 2025
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
lazka
added a commit
that referenced
this issue
Feb 6, 2025
--with-c-locale-coercion otherwise defaults to yes and enables code that isn't compatible on Windows, mainly because the feature is Unix related. Default to "no" on Windows instead. Fixes #36
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Make it a system depended option and default to "no" on Windows. The current default makes the build fail on Windows.
The text was updated successfully, but these errors were encountered: