JDK-8282588: [11] set harfbuzz compilation flag to -std=c++11

[MBaesken]

As a preparation to update harfbuzz in jdk11u-dev to the versions used in higher JDK (harfbuzz 2.7.2 / 2.8.0) increment the C++ version
for harfbuzz to C++11.
Some time later, the harfbuzz changes are backported.
This gives everybody time to make sure the compilers work with the C++11 flag, or system harfbuzz is used as a workaround.

---

Progress

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

Issue

• JDK-8282588: [11] set harfbuzz compilation flag to -std=c++11

Reviewers

• Martin Doerr (@TheRealMDoerr - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk11u-dev pull/853/head:pull/853
$ git checkout pull/853

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 853

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.java.net/jdk11u-dev/pull/853.diff

[bridgekeeper]

👋 Welcome back mbaesken! 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.

[mlbridge]

Webrevs

• 00: Full (147d942e)

[TheRealMDoerr]

LGTM. I had added the flag in the same file when creating my experimental JDK-8247872 backport http://cr.openjdk.java.net/~mdoerr/8247872_harfbuzz_11u/

[openjdk]

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

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

8282588: [11] set harfbuzz compilation flag to -std=c++11

Reviewed-by: mdoerr

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 no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential 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.

[MBaesken]

/integrate

[openjdk]

Going to push as commit 86d39a6.

[openjdk]

@MBaesken Pushed as commit 86d39a6.

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