-
Bug
-
Resolution: Fixed
-
P2
-
9
-
b160
-
windows
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8176609 | 10 | Erik Joelsson | P2 | Resolved | Fixed | b03 |
JDK-8208830 | 8u201 | Kevin Walls | P2 | Resolved | Fixed | b01 |
JDK-8201277 | 8u192 | Kevin Walls | P2 | Closed | Fixed | b01 |
JDK-8284917 | 8u42 | Erik Joelsson | P2 | Resolved | Fixed | b02 |
JDK-8216630 | emb-8u201 | Kevin Walls | P2 | Resolved | Fixed | master |
In our configure code for rewriting cygwin paths reliably, we use this construct to find the root of the cygwin installation:
# The cmd output ends with Windows line endings (CR/LF), the grep command will strip that away
cygwin_winpath_root=`cd / ; cmd /c cd | $GREP ".*"`
This used to work fine for a long time, but with the latest version of cygwin grep, it no longer removes \r from the string. A more robust implementation would be to instead use tr to explicitly remove both \r and \n.
# The cmd output ends with Windows line endings (CR/LF), the grep command will strip that away
cygwin_winpath_root=`cd / ; cmd /c cd | $GREP ".*"`
This used to work fine for a long time, but with the latest version of cygwin grep, it no longer removes \r from the string. A more robust implementation would be to instead use tr to explicitly remove both \r and \n.
- backported by
-
JDK-8176609 New cygwin grep does not match \r as newline
-
- Resolved
-
-
JDK-8208830 New cygwin grep does not match \r as newline
-
- Resolved
-
-
JDK-8216630 New cygwin grep does not match \r as newline
-
- Resolved
-
-
JDK-8284917 New cygwin grep does not match \r as newline
-
- Resolved
-
-
JDK-8201277 New cygwin grep does not match \r as newline
-
- Closed
-
- relates to
-
JDK-8179675 Build with error on windows with new Cygwin grep
-
- Resolved
-
(1 relates to, 2 links to)