Open avelure opened 1 week ago
Running sh C:\msys64\clang64\libexec\nvc\install-uvvm.sh from the win11 commandline gives the same result as from the clang64 mintty.
How about if you try /usr/bin/bash /msys64/clang64/libexec/nvc/install-uvvm.sh
from the clang64 prompt? Also try which bash
and which sh
.
I tried from the native windows11 commandline and then it seems to try to execute the install script with WSL instead of with sh which is in the path from msys.
This is unfortunate. It just picks up the first bash.exe
in the path. Longer term I'd like to replace these shell scripts with TCL as the interpreter is then embedded, but that isn't a hard dependency at the moment.
I tried the install option for uvvm and it seems to have a problem with some path handling. This is from within the clang64 mintty environment
I tried from the native windows11 commandline and then it seems to try to execute the install script with WSL instead of with
sh
which is in the path from msys. This might not be a nvc issue though.Running
sh C:\msys64\clang64\libexec\nvc\install-uvvm.sh
from the win11 commandline gives the same result as from the clang64 mintty.If I
cd /home/arild.velure/.cache/nvc/UVVM-v2024.07.03b/uvvm_util/script/
and do the failing command displayed in the script outputnvc.exe --std=2008 --work=C:/msys64/home/arild.velure/.nvc/lib/uvvm_util.08 -LC:/msys64/home/arild.velure/.nvc/lib -a --relaxed ../src/types_pkg.vhd
it is parsed ok.