0

Don't include sanitizer options for libc++

It breaks component builds since libc++ doesn't actually depend on
these sources. The executable including these symbols should be enough
for them to correctly override ASAN's weak definitions.

Bug: 1321148
Change-Id: I945ebd0853cc9946763becaa3997ff9b021ca433
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3621985
Reviewed-by: Nico Weber <thakis@chromium.org>
Auto-Submit: Leonard Grey <lgrey@chromium.org>
Commit-Queue: Leonard Grey <lgrey@chromium.org>
Cr-Commit-Position: refs/heads/main@{#999442}
This commit is contained in:
Leonard Grey
2022-05-04 16:24:44 +00:00
committed by Chromium LUCI CQ
parent f39480833a
commit 8f4efeed10

@ -145,10 +145,6 @@ target(_libcxx_target_type, "libc++") {
"//build/config/compiler:rtti",
]
if (using_sanitizer) {
configs += [ "//build/config/sanitizers:sanitizer_options_link_helper" ]
}
if (libcxx_is_shared && !is_win) {
configs -= [ "//build/config/gcc:symbol_visibility_hidden" ]
configs += [ "//build/config/gcc:symbol_visibility_default" ]