Nikita Karetnikov <[email protected]> skribis: > build-chroot-dirs = /dev /proc /bin
[...] > ?: 0 [system* "./configure" ...] > > ERROR: In procedure system*: > ERROR: In procedure system*: No such file or directory Is /bin/sh a symlink? If it is, its target has to be in one of the directories listed in ‘build-chroot-dirs’. But more importantly, /bin/sh is likely to be a dynamically-linked executable, linked against stuff from /lib, which is not in ‘build-chroot-dirs’. Thus, it won’t run in the chroot. An option is to replace /bin/sh by the statically-linked Bash that’s in distro/packages/bootstrap/*-linux/bash. Another one, which I think we’ll do, is to change gnu-build-system.scm to either run (system* "/path/to/our/bash" "./configure" ...), or call ‘patch-shebangs’ on ‘configure’. HTH, Ludo’.
