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
Running armhf (armv7l) application on aarch64 processor inside proot #151
Comments
Same here on S10e. Because of that error, I cannot install my system. Everything works great on aarch64.
EDIT: Then it counts links pointing to the group database file: This could be perhaps a bug in hardlink emulation. Here's how it works: #31 (comment) |
Huh, so the issue of that is the hardlink emulation, there could be a workaround for that, rather than using a 32-bit version of proot |
Yep. I'm experimenting a bit.
Expected output (my Arch desktop and aarch64 proot installation from Andronix) is 3. Both executed with Another (unrelated? idk) thing; on aarch64, I see the UID and GUI properly set to 0. On armhf, I get "Uid: (10310/ UNKNOWN) Gid: (10310/ UNKNOWN)" in |
#151 Also configure OFFSETOF_STAT_UID_32 in arch.h to fix second issue reported in #151 (comment)
Looks like I've missed this issue when it was initially reported, sorry. Anyway now I think I have this fixed, for now you can test by building proot from source and if everything is okay then I'll submit to Termux apt repo. It might be necessary to manually remove lock file which could previously became left over. |
Thanks! Strangely enough, Roman's proot-static built for 32b armhf works fine. |
termux/proot#151 link2symlink AArch32 support
Updated version is now available in Termux apt repo |
Hi, i recently installed Ubuntu 32-bit on 64-bit, everything goes well and when trying to start xfce4 session, proot crashes
Somehow the error spits out is about However when using proot static 32-bit, xfce starts fine as intended, though only Tested on Ubuntu, other distributions isn't tested Sorry for any inconveniences if things got worked out recently |
Also happens in Debian Sid 32-bit as well
Somehow this was caused by |
Currently when running in 32-on-64 mode sendmsg calls won't be patched #151 (comment)
termux/proot#151 link2symlink AArch32 support
#151 Also configure OFFSETOF_STAT_UID_32 in arch.h to fix second issue reported in #151 (comment)
Currently when running in 32-on-64 mode sendmsg calls won't be patched #151 (comment)
Hello, is it realistic to fix the launches of the armhf (armv7l) application inside the aarch64 proot system? I noticed that system calls such as statfs generally work crooked in armhf (armv7l) binaries inside the aarch64 proot system.
The text was updated successfully, but these errors were encountered: