-
Notifications
You must be signed in to change notification settings - Fork 59
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
Why does the unused DT entry appear? #26
Comments
It depends on what NDK version you use in combination what Android version you use. If you use Android 7.1 and go back to NDK 21.4.7075529, then the issue should go away by itself. |
OK. Thank you for this answer, but my confusion is as follows: ./configure --prefix=/data/data/com.termux/files/usr/src/nginx As you can see, everything is included for compilation in one program, this time the latest nginx. In the compilation I directly include: "glob.c", "crypt.c", as well as the latest openssl-1.1.1v, zlib-1.3 and pcre2-10.42 from the configuration. So I don't use Termux's libraries, like: "libandroid-glob.so" (I have glob.h and glob.c), "libcrypt.so" (I have crypt.h and crypt.c), "libssl.so.1.1" and "libcrypto.so.1.1" (I have openssl-1.1.1v source code) , "libz.so.1" (I have zlib-1.3 source code) and "libpcre.so" (I have pcre2-10.42 source code). So I only use Termux's compilers "arm-linux-androideabi-clang" and "arm-linux-androideabi-cpp" from "https://packages.termux.dev/termux-main-21/", and everything runs on a device running Android 5.1. Compiled ELF always starts with "WARNING: linker: unused DT entry...". Thank you very much. |
Your versions of arm-linux-androideabi-clang and arm-linux-androideabi-cpp are newer than Android 5.1 and add extra ELF flags for newer versions of android. Use a compiler that is from an older NDK, like NDK 21.4.7075529, if you want those ELF warnings to go away. |
Can someone briefly explain why "WARNING: linker: unused DT entry" appears in compiled programs in Termux?
I have no problem using "termux-elf-cleaner", but can this error be avoided by changing the configuration for "gcc" or "clang"?
Thank you.
The text was updated successfully, but these errors were encountered: