Dan Albert
Dan Albert
I'll keep this open for triage reasons :) Will lock the thread so it's clear that discussion belongs on https://issuetracker.google.com/243471116
Other bug was closed (seemingly a problem with other software on the device, not lldb).
It's only libc (and only the core libc headers at that), and we're trying to get rid of versioner since it prevents https://github.com/android/ndk/issues/837 from working on those headers. I suppose...
Based on the upstream bug, this is not a regression from prior releases, correct? Just a (painful) behavior mismatch between LTO and non-LTO builds?
You can disable fatal linker warnings if you like. We enable them by default in ndk-build and in our CMake toolchain file. From my read of both bugs, the linker...
Upstream bug was fixed early last year. I don't know which NDK that patch will have first shipped in, but the age means it'll be in r27 if not r26.
No. We will post an update when there's an update. We're well aware that people want this, but the infrastructure we need to make it happen just doesn't exist.
Moving to the backlog. I'm no longer convinced that we _should_ do this, since it also automatically enables clang-tidy, and that's probably not something most people want.
https://github.com/android/ndk/wiki/Compatibility
Closing since this library is no longer maintained.