... | @@ -77,7 +77,7 @@ It is very important to put the msys/mingw stuff on your path *before*`c:/window |
... | @@ -77,7 +77,7 @@ It is very important to put the msys/mingw stuff on your path *before*`c:/window |
|
|
|
|
|
**Symptom**: `sh libtool` hangs indefinitely. The process manager shows an extant `cmd` and `sed`, but nothing else. `libtool` is a shell script that comes from a tarball, and is unpacked into `libraries/integer-gmp/gmp/gmpbuild/libtool`
|
|
**Symptom**: `sh libtool` hangs indefinitely. The process manager shows an extant `cmd` and `sed`, but nothing else. `libtool` is a shell script that comes from a tarball, and is unpacked into `libraries/integer-gmp/gmp/gmpbuild/libtool`
|
|
|
|
|
|
**Cause**: `libtool` invokes the following command line (in the function `func_convert_coer_msys_to_w32`:
|
|
**Cause**: `libtool` invokes the following command line (in the function `func_convert_coer_msys_to_w32`):
|
|
|
|
|
|
```wiki
|
|
```wiki
|
|
cmd /c “echo blah”
|
|
cmd /c “echo blah”
|
... | @@ -98,7 +98,9 @@ which does something entirely different, and indeed hangs waiting for input on s |
... | @@ -98,7 +98,9 @@ which does something entirely different, and indeed hangs waiting for input on s |
|
- `msys/1.0/bin` has a little script “cmd” which hands off to the real c:/windows/system32/cmd
|
|
- `msys/1.0/bin` has a little script “cmd” which hands off to the real c:/windows/system32/cmd
|
|
- MSYS does not mangle the command-line for programs in `msys/1.0/bin`
|
|
- MSYS does not mangle the command-line for programs in `msys/1.0/bin`
|
|
- On my old laptop, `msys/1.0/bin` was in my path before `c:/windows/system32`. So plain `cmd` gets the script, and MSYS does not mangle the command line. The script passes arguments on unchanged to the real cmd.
|
|
- On my old laptop, `msys/1.0/bin` was in my path before `c:/windows/system32`. So plain `cmd` gets the script, and MSYS does not mangle the command line. The script passes arguments on unchanged to the real cmd.
|
|
- NB: `c:/windows/system32` is in the “system” path, which precedes the “user” path. So no amount of fiddling with the “user” path will fix this. There are two solutions:
|
|
|
|
|
|
|
|
- Modify the system path
|
|
|
|
- Use a .bashrc file to prepend the stuff you need |
|
NB: `c:/windows/system32` is in the “system” path, which precedes the “user” path. So no amount of fiddling with the “user” path will fix this. There are two solutions:
|
|
|
|
|
|
|
|
- Modify the system path
|
|
|
|
- Use a .bashrc file to prepend the stuff you need |