8289735: UTIL_LOOKUP_PROGS fails on pathes with space

[RealCLanger]

I had to resolve in configure.ac and in basic_tools.m4.

---

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

Issues

• JDK-8289735: UTIL_LOOKUP_PROGS fails on pathes with space
• JDK-8306976: UTIL_REQUIRE_SPECIAL warning on grep

Reviewers

• Matthias Baesken (@MBaesken - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk11u-dev.git pull/1851/head:pull/1851
$ git checkout pull/1851

Update a local copy of the PR:
$ git checkout pull/1851
$ git pull https://git.openjdk.org/jdk11u-dev.git pull/1851/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 1851

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk11u-dev/pull/1851.diff

Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back clanger! 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]

This backport pull request has now been updated with issue from the original commit.

[openjdk]

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

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

8289735: UTIL_LOOKUP_PROGS fails on pathes with space
8306976: UTIL_REQUIRE_SPECIAL warning on grep

Reviewed-by: mbaesken

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 1 new commit pushed to the master branch:

• 42ae833: 8306768: CodeCache Analytics reports wrong threshold

Please see this link for an up-to-date comparison between the source branch of this pull request and 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.

[mlbridge]

Webrevs

• 01: Full - Incremental (22872517)
• 00: Full (2833d9a8)

[RealCLanger]

Adding follow up JDK-8306976 inline.

/issue add 8306976

[openjdk]

@RealCLanger
Adding additional issue to issue list: 8306976: UTIL_REQUIRE_SPECIAL warning on grep.

[RealCLanger]

/integrate

[openjdk]

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

• 26e3971: 8268558: [TESTBUG] Case 2 in TestP11KeyFactoryGetRSAKeySpec is skipped
• 42ae833: 8306768: CodeCache Analytics reports wrong threshold

Your commit was automatically rebased without conflicts.

[openjdk]

@RealCLanger Pushed as commit fc85d95.

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