Hello Mathieu, Mathieu Othacehe skribis: > * gnu/build/vm.scm (define-module): Use module (guix build syscalls). > > It fixes the following warnings during guix build : > > gnu/build/vm.scm:233:3: warning: possibly unbound variable `mount' > gnu/build/vm.scm:238:3: warning: possibly unbound variable `umount' > gnu/build/vm.scm:268:8: warning: possibly unbound variable `mount' > gnu/build/vm.scm:276:8: warning: possibly unbound variable `umount' > gnu/build/vm.scm:315:4: warning: possibly unbound variable `mount' > gnu/build/vm.scm:323:4: warning: possibly unbound variable `umount' This is weird but on purpose: this module is used in a context, in (gnu system vm), where ‘guile-static-stripped’ is running, in the initrd. And ‘guile-static-stripped’ has ‘guile-linux-syscalls.patch’, which adds bindings for ‘mount’, ‘umount’, etc. Conversely, (guix build syscalls) relies on the ability to do dlopen(NULL) and to resolve “mount” et al. from libc.so. This cannot work with the statically-linked Guile, which is why we have ‘guile-linux-syscalls.patch’. So this patch cannot be applied as is, and I think it would break things that use (gnu build vm). That said, we should improve this. Perhaps something along the lines of the attached patch would work. Could you try and send an updated patch? Thanks, Ludo’.