Hi,
Maxim Cournoyer writes:
> Hello again,
>
> Ludovic Courtès writes:
>
> [...]
>
>>> ;; Platforms that QEMU can emulate.
>>> -(define-record-type
>>> - (qemu-platform name family magic mask)
>>> +(define-record-type*
>>
>> Since this is for internal consumption, I’m in favor of keeping pl
Hi!
Vagrant Cascadian skribis:
> That said, it's still a manual step (mounting /gnu or /gnu/store/qemu*)
> required to do something that could otherwise be handled transparently
> with a static build of qemu and adjusting the binfmt_misc flags... so if
> permitted to dream, I still think that wo
On 2019-06-07, Ludovic Courtès wrote:
> Vagrant Cascadian skribis:
>> On Guix there are no flags set, and the binary used is a dynamically
>> linked executable:
>>
>> $ cat /proc/sys/fs/binfmt_misc/qemu-aarch64
>> enabled
>> interpreter
>> /gnu/store/sw2rrqmjij73wcy3ajd47ypvmzh12yz6-qemu-3
Hi!
Vagrant Cascadian skribis:
> On Guix there are no flags set, and the binary used is a dynamically
> linked executable:
>
> $ cat /proc/sys/fs/binfmt_misc/qemu-aarch64
> enabled
> interpreter
> /gnu/store/sw2rrqmjij73wcy3ajd47ypvmzh12yz6-qemu-3.1.0/bin/qemu-aarch64
> flags:
> offs
I've been trying to use qemu-binfmt-service-type to build a non-native
chroot of a Debian system on Guix... because, well... because!
In Debian, this works with the qemu-user-static package, where the
binfmt sets these flags:
$ cat /proc/sys/fs/binfmt_misc/qemu-aarch64
enabled
interpreter /
