You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem finding llvm-analyzer. Seems that the change where the ndkstack.py has been moved in ndkstack.pyz is causing the problem. The function ndkstack.py:get_ndk_path() seems to return incorrect paths, because the pyz-format seem to add directory nesting.
Traceback (most recent call last):
File "/home/ken/android-tools/android-ndk/android-ndk-r26/toolchains/llvm/prebuilt/linux-x86_64/python3/lib/python3.10/runpy.py", line 196, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/home/ken/android-tools/android-ndk/android-ndk-r26/toolchains/llvm/prebuilt/linux-x86_64/python3/lib/python3.10/runpy.py", line 86, in _run_code
exec(code, run_globals)
File "/home/ken/android-tools/android-ndk/android-ndk-r26/prebuilt/linux-x86_64/bin/ndkstack.pyz/__main__.py", line 3, in <module>
File "/home/ken/android-tools/android-ndk/android-ndk-r26/prebuilt/linux-x86_64/bin/ndkstack.pyz/ndkstack.py", line 364, in main
File "/home/ken/android-tools/android-ndk/android-ndk-r26/prebuilt/linux-x86_64/bin/ndkstack.pyz/ndkstack.py", line 93, in find_llvm_symbolizer
OSError: Unable to find llvm-symbolizer
Updating the path detection ndkstack.py with the diff below seems to fix the problem.
This was actually covered by a test, the test was just useless because it was really only testing a mock, which was of course out of date. https://android-review.googlesource.com/c/platform/ndk/+/2764068 fixes the bug, and removes the reliance on the mock so the test will actually catch a regression before it ships in the future.
The fix in the OP was more or less correct, but it was actually ndk_bin that was defined incorrectly, because __file__ is what changed.
Description
Problem finding llvm-analyzer. Seems that the change where the ndkstack.py has been moved in ndkstack.pyz is causing the problem. The function ndkstack.py:get_ndk_path() seems to return incorrect paths, because the pyz-format seem to add directory nesting.
Updating the path detection ndkstack.py with the diff below seems to fix the problem.
Affected versions
r26
Canary version
No response
Host OS
Linux
Host OS version
Debian 11
Affected ABIs
armeabi-v7a, arm64-v8a, x86, x86_64
Build system
ndk-build
Other build system
No response
minSdkVersion
any
Device API level
No response
The text was updated successfully, but these errors were encountered: