Indeed. The architecture contains a 32-bit backward compatible component (that is optional in 64-bit ARM servers[0], but included in the one that you are using) and it is technically possible to install the libraries side by side. However the upstream that Cent is using is intentionally engineered never to support that case. It sounds harsh now, but there is no 32-bit server legacy, we have 32-bit VMs, you could build a 32-bit container if you really wanted, and in a couple of years we will all be wondering why we ever cared about 32-bit in the first place on ARM servers. Jon. [0] That was my doing. It is time to move on from 32-bit and not create a legacy, dragging everyone's power/performance efficiency down having to implement expensive 32-bit backward compatibility that people don't actually need. Recompile the software and move forward. -- Computer Architect | Sent from my 64-bit #ARM Powered phone > On Feb 29, 2016, at 10:51, Jim Perrin <jperrin at centos.org> wrote: > > > > On 02/29/2016 09:20 AM, Michael Howard wrote: > >>> On a semi-related note, is it possible to mount an armv5tel or armv7hl >>> image, and chroot into it? Does that work? Or is aarch64 not binary >>> backward compatible with 32-bit ARM binaries like x86-64 is? >> Just to let you know, I can't get this to work. aarch64 is supposed to >> be binary compatible, with the correct libraries installed, but I'm >> thinking the cpu isn't. >> >> All I get is 'cannot execute binary file: Exec format error', >> regardless of what I try. > > This isn't expected to work currently, no. > > -- > Jim Perrin > The CentOS Project | http://www.centos.org > twitter: @BitIntegrity | GPG Key: FA09AD77 > _______________________________________________ > Arm-dev mailing list > Arm-dev at centos.org > https://lists.centos.org/mailman/listinfo/arm-dev >