Brought this up for discussion with our devs. We haven't yet really gotten that far into ARMv8. I'm not sure that there are too many proprietary pieces of software that require 32 bit on ARM at the moment. We'll probably start with a pure 64 bit environment at the beginning and reevaluate later on when the random software pops up.

Mike Brown

Arch Linux ARM

On Mon, Apr 22, 2013 at 5:15 PM, Mike Frysinger <vapier@gentoo.org> wrote:

On Monday 22 April 2013 16:28:49 Christopher Covington wrote:
> On 04/22/2013 03:11 PM, Mike Frysinger wrote:
> > On Monday 22 April 2013 14:42:44 Christopher Covington wrote:
> >> I'm trying to put together a summary of what distributions have hopped
> >> on the Multiarch /lib/<triplet> bandwagon (or plan to), and for those
> >> who haven't, what their solution is to dealing with various instruction
> >> sets, system call interfaces, application binary interfaces, etc. on a
> >> single root filesystem.
> >
> > Gentoo plans on following standard multilib behavior (what gcc/glibc use)
> >
> > based on the paths before, it looks like you're really only sampling the
> > x86 architecture ?
>
> I'm mostly interested in ARM and x86, but curious about other architectures
> too, if they're handled differently. My thinking as that those who have
> 32-bit ARM support but don't yet have aarch64/arm64 support might adopt
> the same style their x86 support is already using, should they find ARM's
> 64-bit ISA sufficiently interesting.

for Gentoo, we are not going to do reshuffling for aarch64. /lib holds the ARM
32bit libs and /lib64 will hold the aarch64 libs. it'll be this way
regardless of host kernel and default ABI.
-mike