Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

8345744: Use C++ LINK_TYPE with SetupBuildLauncher in StaticLibs.gmk #22624

Closed
wants to merge 2 commits into from

Conversation

jianglizhou
Copy link
Contributor

@jianglizhou jianglizhou commented Dec 7, 2024

Please review following fix for linking static JDK launcher, thanks.

  • Set LINK_TYPE to C++ when building the static launcher to make sure LDCXX instead of LD is used for linking.

  • Remove -l:libstdc++. For linux, -static-libstdc++ is already set in STATIC_STDCXX_FLAGS. See

    STATIC_STDCXX_FLAGS="-static-libstdc++ -static-libgcc"
    .

See more details in https://bugs.openjdk.org/browse/JDK-8345744.


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

Issue

  • JDK-8345744: Use C++ LINK_TYPE with SetupBuildLauncher in StaticLibs.gmk (Bug - P4)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 22624

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

Using diff file

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

Using Webrev

Link to Webrev Comment

… LDCXX instead of LD is used for linking.

- Remove -l:libstdc++. For linux, -static-libstdc++ is set in STATIC_STDCXX_FLAGS. See https://github.com/openjdk/jdk/blob/e0d639878346946d0627a57b0eeb0cac8ca533fc/make/autoconf/lib-std.m4#L50.
@bridgekeeper
Copy link

bridgekeeper bot commented Dec 7, 2024

👋 Welcome back jiangli! 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 Dec 7, 2024

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

8345744: Use C++ LINK_TYPE with SetupBuildLauncher in StaticLibs.gmk

Reviewed-by: ihse

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 20 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 Dec 7, 2024
@openjdk
Copy link

openjdk bot commented Dec 7, 2024

@jianglizhou 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 Dec 7, 2024
@mlbridge
Copy link

mlbridge bot commented Dec 7, 2024

Webrevs

@magicus
Copy link
Member

magicus commented Dec 9, 2024

Thanks @jianglizhou, this was a much better solution. I don't know why I didn't realize that this was the proper solution when I wrote the code.

You can remove STANDARD_LIBS += -lstdc++ from macOS as well. This in turn means that STANDARD_LIBS is not used at all, and can be fully removed.

@jianglizhou
Copy link
Contributor Author

Thanks @jianglizhou, this was a much better solution. I don't know why I didn't realize that this was the proper solution when I wrote the code.

You can remove STANDARD_LIBS += -lstdc++ from macOS as well. This in turn means that STANDARD_LIBS is not used at all, and can be fully removed.

llvm/llvm-project#76945 indicates -static-libstdc++ could be unused on macOS. According to https://docs.brew.sh/C++-Standard-Libraries#:~:text=There%20are%20two%20C++%20standard,you're%20trying%20to%20build., "The default for 10.9 and later is libc++, which is also the default for clang on older platforms when building C++11 code".

Let's not mix the Linux fix with macos and instead address them separately.

@magicus
Copy link
Member

magicus commented Dec 9, 2024

I verified locally that removing -lstdc++ works fine.

In fact, you are already changing macOS, since the LINK_TYPE affects all platforms.

@jianglizhou
Copy link
Contributor Author

jianglizhou commented Dec 9, 2024

I verified locally that removing -lstdc++ works fine.

Thanks for testing it. I also need to re-setup my local macos build environment after changing machine.

In fact, you are already changing macOS, since the LINK_TYPE affects all platforms.

Ok. Removed for now.

Copy link
Member

@magicus magicus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good now!

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Dec 9, 2024
@jianglizhou
Copy link
Contributor Author

Thanks for the review, @magicus!

@jianglizhou
Copy link
Contributor Author

/integrate

@openjdk
Copy link

openjdk bot commented Dec 9, 2024

Going to push as commit a606836.
Since your change was applied there have been 20 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 Dec 9, 2024
@openjdk openjdk bot closed this Dec 9, 2024
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Dec 9, 2024
@openjdk
Copy link

openjdk bot commented Dec 9, 2024

@jianglizhou Pushed as commit a606836.

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

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.

2 participants