-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
build: simplify cc_configure and static link for libc++ #7329
Conversation
Signed-off-by: Lizan Zhou <[email protected]>
Signed-off-by: Lizan Zhou <[email protected]>
@@ -108,7 +59,6 @@ cc_autoconf = repository_rule( | |||
"USE_CLANG_CL", | |||
"CC", | |||
"CFLAGS", | |||
"CXX", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When building with GCC, does the final link happen with gcc
or g++
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
gcc
Signed-off-by: Lizan Zhou <[email protected]>
Signed-off-by: Lizan Zhou <[email protected]>
Signed-off-by: Lizan Zhou <[email protected]>
Signed-off-by: Lizan Zhou <[email protected]>
@jmillikin-stripe @PiotrSikora this is ready now and passes all test, PTAL. |
@@ -118,6 +118,7 @@ envoy_cmake_external( | |||
"ENABLE_LIB_ONLY": "on", | |||
"CMAKE_BUILD_TYPE": "RelWithDebInfo", | |||
"CMAKE_INSTALL_LIBDIR": "lib", | |||
"CMAKE_CXX_COMPILER_FORCED": "on", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't we set CMAKE_C_COMPILER_FORCED
set as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't add it because it wasn't needed, but fine to add as well. no strong opinion on this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, can you verify this doesn't break oss-fuzz? This is a kind of scary change that is worth verifying. Instructions to test are at https://github.com/envoyproxy/envoy/tree/master/test/fuzz#running-fuzz-tests-locally. CC @asraa for fuzz build visibility.
This pull request has been automatically marked as stale because it has not had activity in the last 7 days. It will be closed in 7 days if no further activity occurs. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions! |
This pull request has been automatically closed because it has not had activity in the last 14 days. Please feel free to give a status update now, ping for review, or re-open when it's ready. Thank you for your contributions! |
back from vacation, will check fuzz locally. |
@htuch should be good along with google/oss-fuzz#2586 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
@htuch google/oss-fuzz#2586 is merged, but let's hold merging this until 1.11.0. |
@htuch I'm fine either way, let me see if that PR break fuzz with current master. |
@htuch ah yeah the oss-fuzz breaks, I'm fine merge this, up to you. |
Description: Cherry-picking latest commit of #7329 before release. To unbreak fuzz build. Address #7507 that bring real c++fs dependency. Risk Level: Low Testing: local fuzz, CI Docs Changes: Release Notes: Signed-off-by: Lizan Zhou <[email protected]>
Signed-off-by: Lizan Zhou [email protected]
Description:
Take a similar approach of bazelbuild/bazel@ab9c1f5, which use
-l:libstdc++.a
to statically link libstdc++. This makes us closer to remove our owncc_wrapper
andcc_configure
in the future. Also it will allow us do static link with libc++.Risk Level: Med
Testing: local, CI
Docs Changes:
Release Notes: