-
Bug
-
Resolution: Fixed
-
P3
-
19
-
b26
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8290107 | 17.0.5 | Christoph Langer | P3 | Resolved | Fixed | b01 |
JDK-8297634 | 11.0.18 | Dukebot | P3 | Resolved | Fixed | b05 |
I encountered a bunch of issues when running with msys2 on Windows (but one of them could have happened on cygwin as well).
* fixpath must set MSYS2_ARG_CONV_EXCL="*" before running cmd.exe to figure out the temp directory, or msys might interfere with the command line to cmd.
* Paths like "/c/s/source/jdk", meaning to point to "c:\s\source\jdk", would be interpreted by fixpath as "/cs:\source\jdk", since the leading "/c" would be considered a prefix. This is not a problem on cygwin, where the /cygpath prefix makes paths unambiguous. I countered this by checking if the file exists (as written, or just the basepath, or the first 3 parts of the path). If so, I treat it as a filename, rather than a prefix.
* Configure is supposed to handle windows-style input paths, but `--with-bootjdk=c:\java\jdk-17` or similar would break, since we started to look for files in that directory without having to normalized the path first.
* Finally, configure.guess sometimes reports msys as `mingw` and sometimes as `msys`, depending on the value of MSYSTEM. (And for some values, the old autoconf-configure.guess breaks -- I did not bother fixing this.)
* fixpath must set MSYS2_ARG_CONV_EXCL="*" before running cmd.exe to figure out the temp directory, or msys might interfere with the command line to cmd.
* Paths like "/c/s/source/jdk", meaning to point to "c:\s\source\jdk", would be interpreted by fixpath as "/cs:\source\jdk", since the leading "/c" would be considered a prefix. This is not a problem on cygwin, where the /cygpath prefix makes paths unambiguous. I countered this by checking if the file exists (as written, or just the basepath, or the first 3 parts of the path). If so, I treat it as a filename, rather than a prefix.
* Configure is supposed to handle windows-style input paths, but `--with-bootjdk=c:\java\jdk-17` or similar would break, since we started to look for files in that directory without having to normalized the path first.
* Finally, configure.guess sometimes reports msys as `mingw` and sometimes as `msys`, depending on the value of MSYSTEM. (And for some values, the old autoconf-configure.guess breaks -- I did not bother fixing this.)
- backported by
-
JDK-8290107 Fix various issues with msys2
- Resolved
-
JDK-8297634 Fix various issues with msys2
- Resolved
- links to
-
Commit openjdk/jdk11u-dev/af27be33
-
Commit openjdk/jdk17u-dev/2e21c87f
-
Commit openjdk/jdk/bddef715
-
Review openjdk/jdk11u-dev/1539
-
Review openjdk/jdk17u-dev/541
-
Review openjdk/jdk/8989
(3 links to)