-
-
Notifications
You must be signed in to change notification settings - Fork 18
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
Ubuntu 20.04 aarch64 #51
Comments
Same error also for armhf. |
Please describe your environment in more detail. Thanks. |
In my case, using uraimo/run-on-arch-action@v2 with Ubuntu 24.04. |
Mine was KVM/Qemu Ubuntu 20.04 x86_64 running an aarch64 Ubuntu 20.04 chroot
environment. From a Manjaro host
…On Sun, 19 May 2024, 19:21 probonopd, ***@***.***> wrote:
Please describe your environment in more detail. Thanks.
—
Reply to this email directly, view it on GitHub
<#51 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABONRNVZURAMYXISLFSTW3DZDDUQZAVCNFSM6AAAAABH4OTFQWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJZGMZDANJVHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
FYI, the
Probably appimagetool being compiled as a SYSV executable is what makes the difference. |
Here are some file results from the chroot aarch64 appimagetool-aarch64.AppImage: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), statically linked, stripped
Henry-Stickmin-5-Fleeing-the-Complex-aarch64.AppImage: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, for GNU/Linux 3.7.0, BuildID[sha1]=ecf4dd1f80c620b69e425775ac76171c6976b2c5, stripped From my own tests I can create binary test packages with x86_64 but not aarch 64 as nothing seems to work in my chroot environment? I am also getting the same issues testing on a docker Ubuntu 20.04 aarch64 image. |
Can this issue be reproduced without qemu/kvm and without chroot and without containers, e.g., by running the binary on a Raspberry Pi? Also, on the systems where it is not working, does the old version from https://github.com/AppImage/AppImageKit/ work any better? (It might have to do with the AppImage magic bytes that get inserted into the ELF header, but that is just pure speculation at the moment.) |
I did try the older version and it has the same issue. I tested running them on a native device (rg552 handheld)and it did work. I will dust off my pi and test that too. I was hoping there was something I could do to get it working on my VM, as it's easier to build and package via my chroot environment. But using my pi rather than a VM could work too😀 |
I am trying to test and create some appimages on Ubuntu 20.04 aarch64.
I am running in a chroot environment is that part of the issue with this error?
The text was updated successfully, but these errors were encountered: