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
If, after removing any python3.exe in Windows' PATH, I try opam install conf-python-3 with the mingw64 compilers, either from a full-fledged Cygwin environment, or from a Windows opam with its own copy of Cygwin (under C:\Users\...\AppData\Local\opam\.cygwin\root), then Cygwin python3 installs successfully, but then opam fails with:
#=== ERROR while compiling conf-python-3.9.0.0 ================================#
"python3": command not found.
By contrast, if I install Windows (not Cygwin) Python 3.x "by hand", then opam install conf-python-3 succeeds. But that may not be the result I want, because if I then install an opam package such as z3.4.8.5-1, it fails to compile because of directory separators: \ with Windows Python, but I expect Cygwin / because I expect to compile z3.4.8.5-1 with the Cygwin mingw64 compilers.
I suspect one possible reason may be that opam install is not running with a "full Cygwin PATH environment" such as the one that bash --login would provide. More precisely, python3 should be found as /usr/bin/python3 (a symlink to /etc/alternatives/python3, which is itself a symlink to python), but is not.
I know nothing about windows, and would not be able to test anything related to it. If you have a suggestion to fix this package, it is welcome and others will review it.
This doesn't have an easy solution, I'm afraid. There are two parts to it:
The package installation failure I think - as you suggest - is related to symlink problems, but possibly also to an issue with .exe searching in PATH in opam at the moment.
The problem on the z3 side may need some work with Z3 itself - it would be a lot better if the "Windows" build of Z3 is able to cope with both Python-for-Windows (backslashes) and Python-for-Cygwin (forward-slashes), but there's some more nuance and incentive for sorting that. If opam installs Cygwin's python to it's internal installation, then it's only available during package builds - i.e. not from the Command Prompt or PowerShell instance which ran opam.
If, after removing any python3.exe in Windows' PATH, I try
opam install conf-python-3
with the mingw64 compilers, either from a full-fledged Cygwin environment, or from a Windows opam with its own copy of Cygwin (underC:\Users\...\AppData\Local\opam\.cygwin\root
), then Cygwinpython3
installs successfully, but then opam fails with:By contrast, if I install Windows (not Cygwin) Python 3.x "by hand", then
opam install conf-python-3
succeeds. But that may not be the result I want, because if I then install an opam package such asz3.4.8.5-1
, it fails to compile because of directory separators:\
with Windows Python, but I expect Cygwin/
because I expect to compilez3.4.8.5-1
with the Cygwin mingw64 compilers.Is this related to #26130 ? Thank you in advance @UnixJunkie , @dra27 for clarifying!
Output of
opam var os
:win32
Output of
opam var os-distribution
:cygwin
Output of
opam config report
:The text was updated successfully, but these errors were encountered: