why3 issueshttps://gitlab.inria.fr/why3/why3/-/issues2020-02-25T11:36:40+01:00https://gitlab.inria.fr/why3/why3/-/issues/445why3 commands not recognized on Cygwin+MinGW installation2020-02-25T11:36:40+01:00Ghost Userwhy3 commands not recognized on Cygwin+MinGW installationI installed fdopen's [OCaml for Windows](https://fdopen.github.io/opam-repository-mingw/installation/), which currently installs a `4.09.0+mingw64c` opam repository, and then installed the `why3` package. Installation went fine, but when...I installed fdopen's [OCaml for Windows](https://fdopen.github.io/opam-repository-mingw/installation/), which currently installs a `4.09.0+mingw64c` opam repository, and then installed the `why3` package. Installation went fine, but when I run `why3` with any command, it either does nothing, or does something weird. For instance:
```
$ why3 shell
$ why3 shell
Welcome to Why3 shell. Type 'help' for help.
$
```
The first time, it does nothing, and subsequently, it prints the message but opens no shell.
Trying any command with `--help` outputs the *general* usage message (i.e. the same as `why3 --help`, as if the `config` were not there):
```
$ why3 config --help
Usage: why3 [options]
... (rest omitted)
```
On Linux, the same command outputs the *specific* usage message for the `config` command:
```
Usage: why3 config [options]
... (rest omitted)
```
I cannot, for instance, configure why3, since `why3 config --detect` does nothing other than print the same usage message.
I tried adding `--debug-all`, but it prints nothing other than timing information at the end.
Is there a way to try debugging the issue on Cygwin+MinGW? Anything that could help obtain more details about what is going wrong would be useful (e.g. setting an environment variable, looking for specific binaries...).
I tried both why3 1.2.1 and why3 1.2.0, on switches `4.06.1+mingw64c`, `4.07.0+mingw64c`, and `4.09.0+mingw64c`, and in all cases I have the same issue.
I'm aware the problem may be related to the Windows-based opam repository, but if you could provide some basic information to help debugging, e.g. some sanity checks, it would be very helpful.1.3.0