We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
dotnet core (package dotnet9.0) fails to start with "Error: cannot execute dotnet when renamed to linker64."
pkg install dotnet9.0 dotnet
dotnet starts successfully
Termux Variables: TERMUX_EXEC__PROC_SELF_EXE=/data/data/com.termux/files/usr/bin/termux-info TERMUX_VERSION=googleplay.2025.01.18 TERMUX__USER_ID=0 Packages CPU architecture: aarch64 Subscribed repositories: URIs: https://termux.net Updatable packages: All packages up to date termux-tools version: 3.0.8 Android version: 11 Kernel build information: Linux localhost 4.14.186+ #1 SMP PREEMPT Fri Jun 24 19:54:55 CST 2022 aarch64 Android LD Variables: LD_LIBRARY_PATH= LD_PRELOAD=/data/data/com.termux/files/usr/lib/libtermux-exec.so
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Problem description
dotnet core (package dotnet9.0) fails to start with "Error: cannot execute dotnet when renamed to linker64."
What steps will reproduce the bug?
pkg install dotnet9.0
dotnet
What is the expected behavior?
dotnet starts successfully
System information
Termux Variables: TERMUX_EXEC__PROC_SELF_EXE=/data/data/com.termux/files/usr/bin/termux-info TERMUX_VERSION=googleplay.2025.01.18 TERMUX__USER_ID=0 Packages CPU architecture: aarch64 Subscribed repositories: URIs: https://termux.net Updatable packages: All packages up to date termux-tools version: 3.0.8 Android version: 11 Kernel build information: Linux localhost 4.14.186+ #1 SMP PREEMPT Fri Jun 24 19:54:55 CST 2022 aarch64 Android LD Variables: LD_LIBRARY_PATH= LD_PRELOAD=/data/data/com.termux/files/usr/lib/libtermux-exec.so
The text was updated successfully, but these errors were encountered: