[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Issues installing libc6:arm64 on amd64



> Whatever gave you the idea that arm (aarch64) software, any version,
> compiled for arm would run on amd64 hardware? Different cpu's and
> architectures at the machine code level and they don't speak a
> compatible dialect of native language. Compilers are generally smart
> emough to make the src code work on either platform, but the binaries
> output will be incompatible. At best it will crash.


This is totally off topic, and not what I am trying to do.


Here is an example of what I want to do, just with an example of
installing armhf libraries and binaries.

It works for running armhf on amd64.

$ uname -a
Linux debian 5.7.0-1-amd64 #1 SMP Debian 5.7.6-1 (2020-06-24) x86_64 GNU/Linux
$

$ sudo apt install zstd:armhf liblz4-1:armhf liblzma5:armhf
zlib1g:armhf libstdc++6:armhf

$ file /usr/bin/zstd
/usr/bin/zstd: ELF 32-bit LSB pie executable, ARM, EABI5 version 1
(SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3,
BuildID[sha1]=27f2fcd70757d9607d08566d82284817add19695, for GNU/Linux
3.2.0, stripped

$ qemu-arm /usr/bin/zstd -b /var/log/Xorg.0.log
 3#Xorg.0.log        :     78670 ->     10447 (7.530),  98.3 MB/s , 246.3 MB/s
$

totally works, with binfmt package, it works even more transparent:

$ /usr/bin/zstd -b /var/log/Xorg.0.log
 3#Xorg.0.log        :     78670 ->     10447 (7.530),  97.5 MB/s , 244.5 MB/s
$ file /usr/bin/zstd
/usr/bin/zstd: ELF 32-bit LSB pie executable, ARM, EABI5 version 1
(SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3,
BuildID[sha1]=27f2fcd70757d9607d08566d82284817add19695, for GNU/Linux
3.2.0, stripped
$

The issue is that, for some dependency / packaging reasons, I can't do
the same with arm64.

Also, I never claimed to want to run binaries from arm64 on amd64. I
want to INSTALL multi-arch libraries of arm64 on amd64. Different
things.

Cheers,
Witold

PS. I am now subscribed to the list, so I will be able to properly
respond in the same thread in the future.


Reply to: