Support 32-bit and 64-bit Intel and ARM architectures and (for rpath) musl libc

[probonopd]

Hello.

This idea and approach are awesome! 👍 Would be super helpful in the creation of AppImages, which are self-mounting disk images that execute a bundled, relocatable payload application that may come with its own interpreter. I've been working in this area for a really long time and have always asked myself why 1. glibc keeps changing all the time (breaking compatibility), and 2. why it was not possible to use $ORIGIN to specify a relative path to the interpreter. This project addresses both issues. Hats off! If you ask me, this is how glibc should have been designed in the first place.

The tool is currently only available for x86_64. If other architectures are of interest to you, open a GitHub issue so that we can gauge demand.

Please consider support for 32-bit and 64-bit Intel and ARM architectures and (for the relative path feature only) musl libc. Then we could use it for AppImages like

• appimagetool-aarch64.AppImage (e.g., Raspberry Pi) - what is the status of https://github.com/corsix/polyfill-glibc/tree/main/src/aarch64?
• appimagetool-armhf.AppImage (e.g., original Raspberry Pi) - also see 32-bit ARM support #9
• appimagetool-i686.AppImage (e.g., older 32-bit netbooks) - also see Is it possible to implement a Relative interpreter for i386? #20

Thank you very much!