Skip to content

Conversation

@chiroito
Copy link
Member

@chiroito chiroito commented May 13, 2025

When we run configure on Windows, fixpath is used, but this causes an error if the path contains +.

For example, when we unzip Temurin 24, the directory name created is jdk-24+36. When we specify this as the boot JDK, the following error is output and configure fails

configure: The path of BOOT_JDK_ARG, which is given as “/mnt/d/opt/jdks/temurin-24+36”, cannot be properly resolved.
configure: Please see the section “Special Considerations” in building.md.
configure: This is the error message given by fixpath:
fixpath: failure: Path '/mnt/d/opt/jdks/temurin-24+36' could not be converted to short path
configure: error: Cannot continue

Progress

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Warning

 ⚠️ Found leading lowercase letter in issue title for 8356820: fixpath should allow + in paths on Windows

Issue

  • JDK-8356820: fixpath should allow + in paths on Windows (Enhancement - P4)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/25197/head:pull/25197
$ git checkout pull/25197

Update a local copy of the PR:
$ git checkout pull/25197
$ git pull https://git.openjdk.org/jdk.git pull/25197/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 25197

View PR using the GUI difftool:
$ git pr show -t 25197

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/25197.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented May 13, 2025

👋 Welcome back cito! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented May 13, 2025

@chiroito This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8356820: fixpath should allow + in paths on Windows

Reviewed-by: erikj

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 37 new commits pushed to the master branch:

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

@openjdk openjdk bot added the rfr Pull request is ready for review label May 13, 2025
@openjdk
Copy link

openjdk bot commented May 13, 2025

@chiroito The following label will be automatically applied to this pull request:

  • build

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

@openjdk openjdk bot added the build build-dev@openjdk.org label May 13, 2025
@mlbridge
Copy link

mlbridge bot commented May 13, 2025

Webrevs

@openjdk openjdk bot added the ready Pull request is ready to be integrated label May 13, 2025
@chiroito
Copy link
Member Author

/integrate

@openjdk
Copy link

openjdk bot commented May 14, 2025

Going to push as commit 0c4bc48.
Since your change was applied there have been 53 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label May 14, 2025
@openjdk openjdk bot closed this May 14, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels May 14, 2025
@openjdk
Copy link

openjdk bot commented May 14, 2025

@chiroito Pushed as commit 0c4bc48.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

@magicus
Copy link
Member

magicus commented May 20, 2025

@chiroito
Sorry for coming in late here. While this patch works, and solves your immediate problem, I think it opens more questions than it answers. Most pressing of all: why did the conversion to shortpath fail? That is supposed to be a general method to rewrite any "suspicious" path to a format that is guaranteed to work in make with no ill side effects. I believe adding + to the set of allowed characters is benign, but I did initially keep this set small and restricted, and rather convert to shortpath one time too many than to miss some odd characters that will cause trouble later on.

I would like to know more why + failed, and why we don't see any more information about what was problematic. Especially when run after JDK-8244533 was integrated, more information should be given.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build build-dev@openjdk.org integrated Pull request has been integrated

Development

Successfully merging this pull request may close these issues.

3 participants