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

ghost · 2020-08-10T15:38:52Z

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:

export PREFIX=/data/data/com.termux/files/usr
export LD_LIBRARY_PATH=$PREFIX/lib
export PATH=$PREFIX/bin
termux-upgrade-repo

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

Failsafe shell how-to: https://wiki.termux.com/wiki/Recover_a_broken_environment#Launching_a_Failsafe_Session

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 · 2020-08-11T23:17:51Z

Hey @xeffyr, what does

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?

ghost · 2020-08-11T23:46:39Z

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 · 2020-08-11T23:58:42Z

Yup, can confirm that everything looks OK.

deftdawg · 2020-08-12T07:43:18Z

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

CANNOT LINK EXECUTABLE "cat": library "libandroid-support.so" not found
CANNOT LINK EXECUTABLE "/data/data/com.termux/files/usr/bin/bash": library "libandroid-support.so" not found

[Process completed (code 1) - press Enter]

Seems like the environment shouldn't corrupt itself

Grimler91 · 2020-08-12T08:10:17Z

@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 · 2020-08-13T10:30:10Z

Any shell I open results in this as of Aug 8 build...
CANNOT LINK EXECUTABLE "cat": library "libandroid-support.so" not found
CANNOT LINK EXECUTABLE "/data/data/com.termux/files/usr/bin/bash": library "libandroid-support.so" not found

[Process completed (code 1) - press Enter]
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 · 2020-08-15T22:43:43Z

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.

ghost · 2020-08-15T22:57:53Z

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

What termux-upgrade-repo do is only

Generate reinstallation script
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 · 2020-08-18T23:50:10Z

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

ghost · 2020-08-19T00:44:49Z

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.

Was there one?

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 · 2020-08-19T00:52:06Z

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

kaefer3000 · 2020-08-20T09:01:49Z

@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 · 2020-08-25T19:00:47Z

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 · 2020-08-26T08:11:54Z

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 · 2020-08-26T13:12:24Z

this worked for me with one small change:

Interesting, I didn't run into that - thanks for the extra info.

ghost · 2020-08-26T15:01:57Z

@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 · 2020-09-07T12:16:12Z

export PREFIX=/data/data/com.termux/files/usr
export LD_LIBRARY_PATH=$PREFIX/lib
export PATH=$PREFIX/bin
termux-upgrade-repo

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

export PREFIX=/data/data/com.termux/files/usr
export LD_LIBRARY_PATH=$PREFIX/lib
export PATH=$PREFIX/bin:$PATH
termux-upgrade-repo

Otherwise the script couldn't find chmod.

hg2581 · 2020-09-10T20:27:17Z

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?

ghost · 2020-09-10T20:41:57Z

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.

Open Termux.
Swipe rightwards to open drawer.
Long press on button "New session".
- As in https://wiki.termux.com/wiki/Recover_a_broken_environment#Launching_a_Failsafe_Session.

hg2581 · 2020-09-10T20:52:03Z

On 09/10/2020 04:42 PM, Leonid Pliushch wrote: 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. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1703 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACODNXM6DMP5XIMX23GBFZDSFE22NANCNFSM4P2CXE7Q>.

Hmm, just opened the Termux window again and tried to swipe rightwards in the window but nothing happens. I have the two error messages of course and underneath "[Process completed (signal 6) - press Enter]" Am I missing something?

ghost · 2020-09-10T22:11:36Z

Am I missing something?

Yes,

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.

ghost · 2020-09-10T22:18:44Z

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 · 2020-09-10T22:29:18Z

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 · 2020-09-26T23:26:42Z

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

xonsh: For full traceback set: $XONSH_SHOW_TRACEBACK = True
ModuleNotFoundError: No module named 'prompt_toolkit'
Failed to load xontrib abbrevs.

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!!

ghost added the information label Aug 10, 2020

ghost pinned this issue Aug 10, 2020

ghost mentioned this issue Aug 12, 2020

Update 0.95 to 0.96 messed up on F-droid termux/termux-packages#5686

Closed

ghost mentioned this issue Aug 20, 2020

CANNOT LINK EXECUTABLE "/data/data/com.termux/files/usr/bin/bash": library "libandroid-support.so" not found termux/termux-packages#5714

Closed

ghost closed this as completed Oct 2, 2020

termux locked as resolved and limited conversation to collaborators Oct 2, 2020

ghost unpinned this issue Oct 2, 2020

This issue was closed.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

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

ghost commented Aug 10, 2020 •

edited by ghost

butla commented Aug 11, 2020

ghost commented Aug 11, 2020

butla commented Aug 11, 2020

deftdawg commented Aug 12, 2020

Grimler91 commented Aug 12, 2020

2E0PGS commented Aug 13, 2020

chrylis commented Aug 15, 2020

ghost commented Aug 15, 2020 •

edited by ghost

giner commented Aug 18, 2020

ghost commented Aug 19, 2020

giner commented Aug 19, 2020

kaefer3000 commented Aug 20, 2020 •

edited

ssixty commented Aug 25, 2020 •

edited

petep0p commented Aug 26, 2020

ssixty commented Aug 26, 2020

ghost commented Aug 26, 2020 •

edited by ghost

bensteinberg commented Sep 7, 2020

hg2581 commented Sep 10, 2020

ghost commented Sep 10, 2020

hg2581 commented Sep 10, 2020 via email

ghost commented Sep 10, 2020

ghost commented Sep 10, 2020 •

edited by ghost

hg2581 commented Sep 10, 2020

cauerego commented Sep 26, 2020 •

edited

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

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

Comments

ghost commented Aug 10, 2020 • edited by ghost

What to do:

butla commented Aug 11, 2020

ghost commented Aug 11, 2020

butla commented Aug 11, 2020

deftdawg commented Aug 12, 2020

Grimler91 commented Aug 12, 2020

2E0PGS commented Aug 13, 2020

chrylis commented Aug 15, 2020

ghost commented Aug 15, 2020 • edited by ghost

giner commented Aug 18, 2020

ghost commented Aug 19, 2020

giner commented Aug 19, 2020

kaefer3000 commented Aug 20, 2020 • edited

ssixty commented Aug 25, 2020 • edited

petep0p commented Aug 26, 2020

ssixty commented Aug 26, 2020

ghost commented Aug 26, 2020 • edited by ghost

bensteinberg commented Sep 7, 2020

hg2581 commented Sep 10, 2020

ghost commented Sep 10, 2020

hg2581 commented Sep 10, 2020 via email

ghost commented Sep 10, 2020

ghost commented Sep 10, 2020 • edited by ghost

hg2581 commented Sep 10, 2020

cauerego commented Sep 26, 2020 • edited

ghost commented Aug 10, 2020 •

edited by ghost

ghost commented Aug 15, 2020 •

edited by ghost

kaefer3000 commented Aug 20, 2020 •

edited

ssixty commented Aug 25, 2020 •

edited

ghost commented Aug 26, 2020 •

edited by ghost

ghost commented Sep 10, 2020 •

edited by ghost

cauerego commented Sep 26, 2020 •

edited