fs/cpio: don't fail systems without /dev/null

We pass all our dracut configuration files via a config dir, but dracut
insists with having one config file. Because we do not want to have to
chose which file we pass (which would then have to be excluded from the
config dir), we just used an arbitrary empty file, and /dev/null seemed
to be a good candidate.

However, some build environments do not have a complete /dev, and may be
missing entries otherwise taken for granted, like /dev/null. This is
especially the case in constrained environments like containers.

Switch away from using /dev/null, and do create an actual empty file
that we can use as the dracut config file.

Fixes:

  https://gitlab.com/buildroot.org/buildroot/-/jobs/3249828364

Reported-by: Thomas Petazzoni <[email protected]>
Signed-off-by: Yann E. MORIN <[email protected]>
Signed-off-by: Thomas Petazzoni <[email protected]>

diff --git a/fs/cpio/cpio.mk b/fs/cpio/cpio.mk
index d671c337dfedb8ba803859fa24ff258b84101a82..061f4a18f18e4ac97340a2a8976ac0214c3086f3 100644 (file)
--- a/fs/cpio/cpio.mk
+++ b/fs/cpio/cpio.mk
@@ -69,12 +69,13 @@ endif
 
 define ROOTFS_CPIO_CMD
        mkdir -p $(ROOTFS_CPIO_DIR)/tmp $(ROOTFS_CPIO_DIR)/confdir
+       touch $(ROOTFS_CPIO_DIR)/empty-config
        $(foreach cfg,$(ROOTFS_CPIO_DRACUT_CONF_FILES), \
                cp $(cfg) $(ROOTFS_CPIO_DIR)/confdir/$(notdir $(cfg))
        )
        $(HOST_DIR)/bin/dracut \
                $(ROOTFS_CPIO_OPTS) \
-               -c /dev/null \
+               -c $(ROOTFS_CPIO_DIR)/empty-config \
                --confdir $(ROOTFS_CPIO_DIR)/confdir \
                --sysroot $(TARGET_DIR) \
                --tmpdir $(ROOTFS_CPIO_DIR)/tmp \