Le 12/05/2022 à 18:16, John Paul Adrian Glaubitz a écrit :
Hi!
Hi :)
On 5/12/22 18:10, Laurent Vivier wrote:The flags are correct. This can be tested with: $ sudo chroot m68k-chroot sh -c 'echo $0' sh if the argument is not properly managed, you would have "/usr/bin/sh".OK, this is working properly: root@z6:/srv/chroot> chroot unstable-m68k-sbuild/ sh -c 'echo $0' sh root@z6:/srv/chroot> I guess it's related to the glibc issue then [1].
You can try by mounting your chroot on a non ext4 partition. It works well with btrfs.Ext4 stores a hash in a field that is normally an index, so a 64bit (host kernel long) hash cannot be passed to the 32bit guest.
btrfs uses it as a real index, so it will overflow only with 2³² entries. Thanks, Laurent
Adrian[1] https://sourceware.org/bugzilla/show_bug.cgi?id=23960