Hmm I tried it but it seems more broken than that:
patb@DESKTOP-REQM4CB MSYS ~
$ pacman -Syuu
patb@DESKTOP-REQM4CB MSYS ~
$ which pacman
/usr/bin/pacman
patb@DESKTOP-REQM4CB MSYS ~
$ file /usr/bin/pacman
/usr/bin/pacman: PE32+ executable (console) x86-64 (stripped to external
PDB), for MS Windows
patb@DESKTOP-REQM4CB MSYS ~
$ pacman -hl
It's weird, some things (the built-ins?) seem to work, and others do nowt.
'env' works, 'vim' does nothing.
There don't seem to be obvious dependencies missing. This looks OK:
patb@DESKTOP-REQM4CB MSYS ~
$ ldd /usr/bin/pacman
ntdll.dll => /c/Windows/SYSTEM32/ntdll.dll (0x7ffca2930000)
KERNEL32.DLL => /c/Windows/System32/KERNEL32.DLL (0x7ffc9fea0000)
KERNELBASE.dll => /c/Windows/System32/KERNELBASE.dll
(0x7ffc9f500000)
msys-2.0.dll => /usr/bin/msys-2.0.dll (0x180040000)
bcrypt.dll => /c/Windows/SYSTEM32/bcrypt.dll (0x7ffc9e7e0000)
I tried re-running the powershell script, but it doesn't think it has
anything to do.
Perhaps recent Windows 10 updates have brought to quarantine the pacman
executable, or something weird like that.
I guess I will have another play-around & try and see what's going on later.
Thanks again for the advice, David.
Cheers
Patrick
--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-Dev-f1435356.html
_______________________________________________
gnucash-devel mailing list
[email protected]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
