8304291: [AIX] Broken build after JDK-8301998

[backwaterred]

Backport of this patch to address build errors on xlclang v16 build errors after Harfbuzz upgrade.

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8304291: [AIX] Broken build after JDK-8301998

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 57

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk20u/pull/57.diff

Webrev

Link to Webrev Comment

[bridgekeeper]

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

@backwaterred 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:

8304291: [AIX] Broken build after JDK-8301998

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:

• 6db9050: 8297587: Upgrade JLine to 3.22.0

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.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[mlbridge]

Webrevs

• 00: Full (376bd15e)

[backwaterred]

/integrate

[openjdk]

@backwaterred
Your change (at version 376bd15) is now ready to be sponsored by a Committer.

[shipilev]

Looks fine. The push approval is there.

/integrate

[shipilev]

Um.

/sponsor

[openjdk]

@shipilev Only the author (@backwaterred) is allowed to issue the integrate command. As this pull request is ready to be sponsored, and you are an eligible sponsor, did you mean to issue the /sponsor command?

[openjdk]

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

• b63e16e: 8306543: GHA: MSVC installation is failing
• 6db9050: 8297587: Upgrade JLine to 3.22.0

Your commit was automatically rebased without conflicts.

[openjdk]

@shipilev @backwaterred Pushed as commit c0604cb.

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

[backwaterred]

Thanks @shipilev :-)