On 8/26/21 11:14, Frans de Boer wrote:
On 8/26/21 10:19, Andreas Schwab wrote:
On Aug 26 2021, Frans de Boer wrote:
I was not sure, but I tried the same also with x86_64 cross compiled
programs using qemu-i386, which worked.
Of course, they can be natively executed.
Andreas.
I understand
On 8/26/21 10:19, Andreas Schwab wrote:
On Aug 26 2021, Frans de Boer wrote:
I was not sure, but I tried the same also with x86_64 cross compiled
programs using qemu-i386, which worked.
Of course, they can be natively executed.
Andreas.
I understand now better how things are connected.
On Aug 26 2021, Frans de Boer wrote:
> I was not sure, but I tried the same also with x86_64 cross compiled
> programs using qemu-i386, which worked.
Of course, they can be natively executed.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510
On 8/26/21 01:25, Assaf Gordon wrote:
tag 50151 notabug
close 50151
stop
On 2021-08-25 12:54 p.m., Frans de Boer wrote:
On 8/25/21 10:16 AM, Assaf Gordon wrote:
qemu-aarch64 -strace -L /newroot \
/newroot/usr/sbin/chroot /newroot /usr/bin/env --version 2&1 \
| tee log.txt
tag 50151 notabug
close 50151
stop
On 2021-08-25 12:54 p.m., Frans de Boer wrote:
On 8/25/21 10:16 AM, Assaf Gordon wrote:
qemu-aarch64 -strace -L /newroot \
/newroot/usr/sbin/chroot /newroot /usr/bin/env --version 2&1 \
| tee log.txt
@assaf: your suggestions no. 1 and 2,
On 8/25/21 10:16 AM, Assaf Gordon wrote:
Hello,
On 2021-08-24 2:39 a.m., Paul Eggert wrote:
However, I think it'll be a better use of our time for you to debug
this one yourself. It doesn't sound like a Coreutils problem; it
sounds like a problem in your virtual machine setup, and you're the
Hello,
On 2021-08-24 2:39 a.m., Paul Eggert wrote:
However, I think it'll be a better use of our time for you to debug this
one yourself. It doesn't sound like a Coreutils problem; it sounds like
a problem in your virtual machine setup, and you're the best expert on
that setup.
Few
On 8/21/21 6:43 PM, Paul Eggert wrote:
On 8/21/21 3:33 AM, Frans de Boer wrote:
So, I guess chroot is to blame?
Seems unlikely that it'd be a coreutils bug. Possibly you simply have
the wrong type of executable installed as /newroot/usr/sbin/chroot.
If it is a coreutils bug, please give
On 8/24/21 1:31 AM, Frans de Boer wrote:
If it is the wrong executable, would it ever startup and continue and
(try to) load bash or env?
No.
It even displays the help message!
Not from what you've shown so far. You reported the output of env
--help, not the output of chroot --help.
I
On 8/21/21 3:33 AM, Frans de Boer wrote:
So, I guess chroot is to blame?
Seems unlikely that it'd be a coreutils bug. Possibly you simply have
the wrong type of executable installed as /newroot/usr/sbin/chroot.
If it is a coreutils bug, please give complete steps to let others
reproduce
LS,
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
11 matches
Mail list logo
