-
-
Notifications
You must be signed in to change notification settings - Fork 581
Closed
Description
So I was trying to build an appimage for aarm64 (using Debian on a VM inside Mac M1) and this happened:
debian@debian:~/dockie$ ARCH=aarch64 ./appimagetool-aarch64.AppImage -v AppDir
appimagetool, continuous build (commit a2d9cfc), build <local dev build> built on 2021-11-10 17:45:57 UTC
WARNING: appstreamcli command is missing, please install it if you want to use AppStream metadata
Desktop file: /home/debian/dockie/AppDir/dockie.desktop
Name: dockie
Icon: dockie
Exec: dockie
Comment entry not found in desktop file
Comment: (null)
Type: Application
Categories: Development;
/home/debian/dockie/AppDir/usr/bin/graboid used for determining architecture aarch64
/home/debian/dockie/AppDir/usr/bin/proot used for determining architecture aarch64
/home/debian/dockie/AppDir/AppRun used for determining architecture armhf
More than one architectures were found of the AppDir source directory "AppDir"
A valid architecture with the ARCH environmental variable should be provided
e.g. ARCH=x86_64 appimagetool ...
debian@debian:~/dockie$ file AppDir/usr/bin/graboid AppDir/AppRun
AppDir/usr/bin/graboid: ELF 64-bit LSB executable, ARM aarch64, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-aarch64.so.1, Go BuildID=0hBGcJft_XngBwEomgEP/Tgva4mrJXsxfaTAjDikq/DCcYhILPVrat2ooRlxX7/snYc6Ie_YCcsfCZ43w3S, not stripped
AppDir/AppRun: POSIX shell script, ASCII text executable
debian@debian:~/dockie$ uname -m
aarch64
so my system is aarch64, my binaries are all aarch64 but I can't build my AppImage because it considers that my bash script has a different architecture, is this a bug or am I doing something wrong?
Metadata
Metadata
Assignees
Labels
No labels