[Top][All Lists]

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

bug#50151: Coreutils, aarch64 and chroot

From: Frans de Boer
Subject: bug#50151: Coreutils, aarch64 and chroot
Date: Sat, 21 Aug 2021 12:33:29 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0


I have an issue with chroot in the next context:

qemu-aarch64 -cpu cortex-a53 -L /newroot /newroot/usr/sbin/chroot /newroot \
  /usr/bin/env -i \
    HOME=/root \
    TERM="$TERM" \
    PS1='(arm chroot) \u:\w\$ ' \
    PATH=/usr/bin:/usr/sbin \
    /usr/bin/bash --login +h

qemu-aarch64 is running on top of x86_64 linux and chroot, env and bash are compiled as aarch64 binaries. By themselves they all run under qemu-aarch64. But when using the above command, it always fails with 'Exec format error'. The same if running:

qemu-aarch64 -L /newroot /newroot/usr/sbin/chroot /newroot

It should run /bin/bash, but ends with the same error message.

Running 'qemu-aarch64 -L /newroot /newroot/usr/bin/bash -c /usr/bin/env --help' does show the env help text. So, I guess chroot is to blame?

Regards, Frans.

A: Yes, just like that                            A: Ja, net zo
Q: Oh, Just like reading a book backwards         Q: Oh, net als een boek 
achterstevoren lezen
A: Because it upsets the natural flow of a story  A: Omdat het de natuurlijke 
gang uit het verhaal haalt
Q: Why is top-posting annoying?                   Q: Waarom is Top-posting zo 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]