Cannot link executable android

libandroid-support error: CANNOT LINK EXECUTABLE . cannot locate symbol «nl_langinfo» referenced by . #3283

Comments

steffenl82 commented Jan 27, 2019

Today while doing an «apt update» and «apt ugrade» I got an upgrade for libandroid-support.

Now my termux installation is completely inaccessible.

When I try to start termux I get the following message and the program immediately terminates:

«CANNOT LINK EXECUTABLE «/data/data/com.termux/files/usr/bin/bash»: cannot locate symbol «nl_langinfo» referenced by «/data/data/com.termux/files/usr/lib/libreadline.so.7.0». «

Any help would be highly appreciated! Thank you.

The text was updated successfully, but these errors were encountered:

Grimler91 commented Jan 27, 2019

What device do you have, is it arm, aarch64 or other?

steffenl82 commented Jan 27, 2019

it is an arm device

Grimler91 commented Jan 27, 2019 •

(Oh yeah, you apparently wrote that in the title.. 🙂 )

You can downgrade libandroid-support temporarily until is fixed by:

• opening a failsafe session: https://wiki.termux.com/wiki/Recover_a_broken_environment#Launching_a_Failsafe_Session
• setting up environment: export PATH=$PREFIX/bin:$PATH; export LD_LIBRARY_PATH=$PREFIX/lib
• download libandroid-support 22: curl -LO https://grimler.se/dists/testing/misc/binary-arm/libandroid-support_22-1_arm.deb . If your arch isn’t arm then replace arm in binary-arm and libandroid-support_22-1_arm.deb with your arch.
• install old version: dpkg -i ./libandroid-support_22-1_arm.deb
• restart the app

And then avoid apt upgrade for a while (or use apt-mark hold libandroid-support )
An updated libandroid-support has been pushed to the repo so running apt update && apt upgrade after restoring the old libandroid-support will fix everything

Источник

Address Sanitizer on Android : CANNOT LINK EXECUTABLE «crash_dump64»: «/data/local/tmp/libclang_rt.asan-i686-android.so» is 32-bit instead of 64-bit #1103

Comments

sarora5 commented Jun 3, 2019

I am trying to enable ASAN on 32 bit app(x86) running on x86_64 emulator.

My Wrap,sh Script looks like :

#!/system/bin/sh
HERE=»$(cd «$(dirname «$0″)» && pwd)»
export ASAN_OPTIONS=allow_user_segv_handler=1
export ASAN_OPTIONS=»$ASAN_OPTIONS:verbosity=1:debug=1″
export LD_PRELOAD=$HERE/libclang_rt.asan-i686-android.so
exec «$@»

I am executing following script before installing my app:

adb shell su 0 setenforce 0
adb push «$NDK_PATH/toolchains/llvm/prebuilt/linux-x86_64/lib64/clang/7.0.0/lib/linux/libclang_rt.asan-i686-android.so» /data/local/tmp
adb push «$NDK_PATH/sources/cxx-stl/llvm-libc++/libs/x86/libc++_shared.so» /data/local/tmp
adb push «$WRAP_SCRIPT_PATH/wrap.sh /data/local/tmp
adb shell chmod +x /data/local/tmp/wrap.sh
adb shell su 0 setprop wrap.com.xxxx.»$1″ /data/local/tmp/wrap.sh

I am getting following error all the time :

06-03 19:34:24.297 19817 19817 F libc : CANNOT LINK EXECUTABLE «crash_dump64»: «/data/local/tmp/libclang_rt.asan-i686-android.so» is 32-bit instead of 64-bit
06-03 19:34:24.297 19817 19817 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 19817 (crash_dump64)
06-03 19:34:24.298 19819 19819 F libc : CANNOT LINK EXECUTABLE «crash_dump64»: «/data/local/tmp/libclang_rt.asan-i686-android.so» is 32-bit instead of 64-bit
06-03 19:34:24.298 19819 19819 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 19819 (crash_dump64)
06-03 19:34:24.300 19821 19821 F libc : CANNOT LINK EXECUTABLE «crash_dump64»: «/data/local/tmp/libclang_rt.asan-i686-android.so» is 32-bit instead of 64-bit
06-03 19:34:24.300 19821 19821 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 19821 (crash_dump64)
06-03 19:34:24.301 19823 19823 F libc : CANNOT LINK EXECUTABLE «crash_dump64»: «/data/local/tmp/libclang_rt.asan-i686-android.so» is 32-bit instead of 64-bit
06-03 19:34:24.301 19823 19823 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 19823 (crash_dump64)
06-03 19:34:24.303 19825 19825 F libc : CANNOT LINK EXECUTABLE «crash_dump64»: «/data/local/tmp/libclang_rt.asan-i686-android.so» is 32-bit instead of 64-bit
06-03 19:34:24.303 19825 19825 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 19825 (crash_dump64)
06-03 19:34:24.304 19827 19827 F libc : CANNOT LINK EXECUTABLE «crash_dump64»: «/data/local/tmp/libclang_rt.asan-i686-android.so» is 32-bit instead of 64-bit
06-03 19:34:24.304 19827 19827 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 19827 (crash_dump64)
06-03 19:34:24.306 19829 19829 F libc : CANNOT LINK EXECUTABLE «crash_dump64»: «/data/local/tmp/libclang_rt.asan-i686-android.so» is 32-bit instead of 64-bit
06-03 19:34:24.306 19829 19829 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 19829 (crash_dump64)
06-03 19:34:24.307 19831 19831 F libc : CANNOT LINK EXECUTABLE «crash_dump64»: «/data/local/tmp/libclang_rt.asan-i686-android.so» is 32-bit instead of 64-bit
06-03 19:34:24.307 19831 19831 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 19831 (crash_dump64)
06-03 19:34:24.308 19833 19833 F libc : CANNOT LINK EXECUTABLE «crash_dump64»: «/data/local/tmp/libclang_rt.asan-i686-android.so» is 32-bit instead of 64-bit
06-03 19:34:24.309 19833 19833 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 19833 (crash_dump64)
06-03 19:34:24.310 19835 19835 F libc : CANNOT LINK EXECUTABLE «crash_dump64»: «/data/local/tmp/libclang_rt.asan-i686-android.so» is 32-bit instead of 64-bit
06-03 19:34:24.310 19835 19835 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 19835 (crash_dump64)

The text was updated successfully, but these errors were encountered:

Источник

Read this, if you have «CANNOT LINK EXECUTABLE» after update #1703

Comments

xeffyr commented Aug 10, 2020 •

Version 0.96 and higher of Termux application removes support of so-called «legacy environment» (set of packages used for Android 5.x-6.x). Packages installed from https://termux.net will no longer work. Packages mixed from https://termux.net and other sources will no longer work too.

What to do:

Open failsafe shell, copy important files to /sdcard and then erase Termux application data.

Alternatively, you may attempt to use termux-upgrade-repo script from failsafe shell:

If no termux-upgrade-repo available, follow #1703 (comment).

P.S. Another major environment update is coming soon, including packaging format change. Brief info is available at https://github.com/termux/termux-packages/wiki/Termux-and-Android-10.

The text was updated successfully, but these errors were encountered:

butla commented Aug 11, 2020

You may attempt to use termux-upgrade-repo script from failsafe shell:

mean? To do it instead of erasing Termux application data? Or after it? What is the purpose of termux-upgrade-repo ?

xeffyr commented Aug 11, 2020

Yes, instead of completely erasing data. termux-upgrade-repo will erase only $PREFIX, data of $HOME won’t be touched and will generate a script for reinstalling packages.

butla commented Aug 11, 2020

Yup, can confirm that everything looks OK.

deftdawg commented Aug 12, 2020

Any shell I open results in this as of Aug 8 build.

Seems like the environment shouldn’t corrupt itself

Grimler91 commented Aug 12, 2020

@deftdawg environment broke after termux-app was updated, but packages have not been updated for 8 months.

If you want to ensure environment does not break then either never update app or packages, or keep both up to date.

2E0PGS commented Aug 13, 2020

Any shell I open results in this as of Aug 8 build.

Seems like the environment shouldn’t corrupt itself

I had the exact same issue. One day it just corruped itself with same error as you. I didn’t recently install or upgrade any packages inside termux.

To fix it, I just uninstalled and reinstalled the app. You do however loose the previous termux file system contents. Annoying but seems specific to older installation since my newer phone’s termux never corrupted itself.

chrylis commented Aug 15, 2020

termux-upgrade-repo: not found

This has been a really frustrating experience for no good reason. I wasn’t aware that I needed to perform a manual upgrade step just to keep bash running, and nothing in the upgrade process ever notified me. Now the recommended fix not only doesn’t work, but apparently couldn’t possibly work.

xeffyr commented Aug 15, 2020 •

Now the recommended fix not only doesn’t work, but apparently couldn’t possibly work.

What termux-upgrade-repo do is only

1. Generate reinstallation script
2. rm -rf $PREFIX
   That’s ALL!

It may not exist if environment is very outdated or is a mix of packages from termux.net and bintray.

I wasn’t aware that I needed to perform a manual upgrade step

Have you ever run pkg upgrade ? If you did that periodically, then motd message would be switched to one claimin that you are running «legacy environment». Btw, there were more than a half of year between legacy environment deprecation (01.01.2020) and final drop.

Keeping environment out-of-sync with app will broke it at some point because environment is not independent. Either update both or do not update at all.

giner commented Aug 18, 2020

Somehow while using termux almost everyday I hadn’t noticed a deprecation warning before everything broke. Was there one?

xeffyr commented Aug 19, 2020

Somehow while using termux almost everyday I hadn’t noticed a deprecation warning before everything broke.

Everyday, without updating packages and even without checking community pages. That’s why you have not been notified.

Significant changes are always posted on community pages and, if needed, being sent as update of termux-tools package which provides a motd displayed during session startup.

Everyone who has up-to-date packages of https://termux.net, will have a warning about legacy environment usage. Commit termux/termux-packages@97b5924.

I have also did an announcement about deprecation of Android 5/6 compatibility branch on Github (termux/termux-packages#4467) and Reddit https://www.reddit.com/r/termux/comments/dnzdbs/end_of_android56_support_on_20200101/.

giner commented Aug 19, 2020

I do update termux itself from F-Droid regularly but not packages

kaefer3000 commented Aug 20, 2020 •

@chrylis the following helped me:

• copy the missing script from https://github.com/termux/termux-packages/blob/android-5/packages/termux-tools/termux-upgrade-repo to your device
• edit the file such that the variable PREFIX points to the right directory
• do as described in the other instructions

ssixty commented Aug 25, 2020 •

Thanks kafer but your instructions are still a little vague, I was getting errors that chmod couldn’t be found. here’s exactly what I did in the end — don’t refer to the instructions in OP at all.

• got the script https://github.com/termux/termux-packages/blob/android-5/packages/termux-tools/termux-upgrade-repo and changed the line to PREFIX=/data/data/com.termux/files/usr
• copied it to my device with a file manager app
• started Termux failsafe mode, moved the script to my home directory and made it executable: chmod +x
• ran the script.
• restarted termux and waited for it to install things.
• reinstalled openssh and any other packages I use.

petep0p commented Aug 26, 2020

Thanks kafer but your instructions are still a little vague, I was getting errors that chmod couldn’t be found. here’s exactly what I did in the end — don’t refer to the instructions in OP at all.

• got the script https://github.com/termux/termux-packages/blob/android-5/packages/termux-tools/termux-upgrade-repo and changed the line to PREFIX=/data/data/com.termux/files/usr
• copied it to my device with a file manager app
• started Termux safe mode, moved the script to my home directory and made it executable: chmod +x
• ran the script.
• restarted termux and waited for it to install things.
• reinstalled openssh and any other packages I use.

this worked for me with one small change:
#!/system/bin/sh
should be the initial line rather than just /bin/sh
it kept saying «No such file or directory» when I tried to execute, and i was like «but it’s right there!». it took me forever to realize that it wasn’t the script itself, but sh that wasn’t found.

ssixty commented Aug 26, 2020

this worked for me with one small change:

Interesting, I didn’t run into that — thanks for the extra info.

xeffyr commented Aug 26, 2020 •

@ssixty Because script uses #!/bin/sh as default shebang. It is being rewritten into something like #!/data/data/com.termux/files/usr/bin/sh during packaging of termux-tools . As some devices (and probably yours) have /bin symlinked to /system/bin , ./termux-upgrade-repo may get executed without issues even if default shebang was used.

bensteinberg commented Sep 7, 2020

@xeffyr’s instructions above worked for me with the following change, adding the existing $PATH to the new one:

Otherwise the script couldn’t find chmod .

hg2581 commented Sep 10, 2020

I am on Android 7.1.2 and ran into this issue a couple of weeks ago. While I had noticed fr some time that various apps were no longer upgraded when I typed pkg upgrade, I had no idea that the entire termux setup would collapse. I just checked and I am running version 0.98 of termux on this tablet.

Anyway, I found this page and looked for the failsafe-shell and cannot find it. As pointed out, running Android 7 there is no failsafe-shell option when long-pressing the app icon but more importantly, there is no menu after loading termux where I can start this failsafe-shell. Instead. I am staring at the error messages and cannot see that I can get past them.

So, how do I get to the failsafe-shell and then proceed to recover a working termux setup on my tablet?

xeffyr commented Sep 10, 2020

So, how do I get to the failsafe-shell and then proceed to recover a working termux setup on my tablet?

There 2 ways for accessing failsafe shell: through drawer and with shortcut. Shortcuts displaying depends on used launcher and OS. So you stick to drawer option.

1. Open Termux.
2. Swipe rightwards to open drawer.
3. Long press on button «New session».
   — As in https://wiki.termux.com/wiki/Recover_a_broken_environment#Launching_a_Failsafe_Session.

xeffyr commented Sep 10, 2020

• You didn’t read the instructions or do not understand them.
• Or you just use a very special Termux which doesn’t have anything except terminal window.

xeffyr commented Sep 10, 2020 •

I understand that reading text may be very difficult (btw, why using Termux in this case. ), so here is a video: https://imgur.com/a/xIBiW2c

Added to https://wiki.termux.com/wiki/Recover_a_broken_environment. I was sure that everyone can read the article properly.

hg2581 commented Sep 10, 2020

No need to be sarcastic and the video also did not show exactly where to start swiping. I now began swiping a little past the left edge of the terminal window and was able to launch a failsafe session. I’ll see where it goes from here.

cauerego commented Sep 26, 2020 •

just wanted to point for future reference that i was having an issue with xonsh and some corrupted configuration from xconfig web , i believe:

which brought me to a similar status unable to use termux.

and finding out about the failsafe here was the missing piece for me! 🤣

i knew there should be some such way to fix it, but just couldn’t find it anywhere else!!

Источник