ludo@gnu.org (Ludovic Courtès) writes:

> The ABI and file format are entirely (or almost entirely) the
> responsibility of user-land software (how you configure the toolchain
> determines what ABI you use, for instance.)  Thus they’re necessarily
> captured by the dependency graph; no need to store that information
> elsewhere.
>
> ...
> 
> It’s the toolchain that shows up in the graph that determines what ABI
> is targeted.

The Guix manual makes it sound like the Guix system string can identify
more than just the CPU architecture and kernel.  Specifically, in the
section titled "GNU Distribution", it says the following:

‘armhf-linux’
     ARMv7-A architecture with hard float, Thumb-2 and NEON, using the
     EABI hard-float application binary interface (ABI), and Linux-Libre
     kernel.

‘aarch64-linux’
     little-endian 64-bit ARMv8-A processors, Linux-Libre kernel.  This
     is currently in an experimental stage, with limited support.  *Note
     Contributing::, for how to help!

‘mips64el-linux’
     little-endian 64-bit MIPS processors, specifically the Loongson
     series, n32 ABI, and Linux-Libre kernel.


Is this langugae too specific?

-- 
Chris