Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#77783 - [qemu-user-static] Appears to not be compiled statically
Attached to Project:
Arch Linux
Opened by Alex Davies (traverseda) - Wednesday, 08 March 2023, 17:16 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 08 March 2023, 21:53 GMT
Opened by Alex Davies (traverseda) - Wednesday, 08 March 2023, 17:16 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 08 March 2023, 21:53 GMT
|
DetailsDescription:
So the main reason for this is using it in a chroot, as described in this wiki page: https://wiki.archlinux.org/title/QEMU#Chrooting_into_arm/arm64_environment_from_x86_64 Unfornatly trying to follow the instructions in that article results in `qemu-aarch64-static: Could not open '/lib/ld-linux-aarch64.so.1': No such file or directory` Additional info: * 7.2.0-3 Steps to reproduce: Wiki article describes steps to reproduce here: https://wiki.archlinux.org/title/QEMU#Chrooting_into_arm/arm64_environment_from_x86_64 As this involves setting up an arm based rootfs to chroot into I'll leave the specifics up to the reader. |
This task depends upon
Closed by Toolybird (Toolybird)
Wednesday, 08 March 2023, 21:53 GMT
Reason for closing: Not a bug
Additional comments about closing: See comments
Wednesday, 08 March 2023, 21:53 GMT
Reason for closing: Not a bug
Additional comments about closing: See comments
Comment by Toolybird (Toolybird) -
Wednesday, 08 March 2023, 21:52 GMT
The binary is most definitely statically linked which you can easily verify using "file", "readelf" etc. AFAIK folks are successfully doing what you are trying to do so this appears to be a procedural problem on your end. For support, please use the proper support channels (forum/IRC/etc) to seek help in identifying the cause.