Genkernel prints error and exits when trying to use --mdadm option. Reproducible: Always Steps to Reproduce: Run: genkernel --loglevel=5 --mdadm --menuconfig all Actual Results: Genkernel prints error and exits Expected Results: Genkernel should build the kernel Genkernel log: * CMD_LOGLEVEL: 5 * CMD_MDADM: yes * ERROR: parse_cmdline(): print_warning(): Invalid usage of print_info(): Function takes at least two arguments (1 given)! * Report any genkernel bugs to bugs.gentoo.org and * assign your bug to genkernel@gentoo.org. Please include * as much information as you can in your bug report; attaching * '/var/log/genkernel.log' so that your issue can be dealt with effectively. * * Please do *not* report kernel compilation failures as genkernel bugs! * * --no-cleanup is set; Skipping cleanup ... * TEMP: * CACHE_DIR: /var/cache/genkernel * TMPDIR: /usr/share/genkernel/gen_funcs.sh: line 429: let: GK_TIME_RUNTIME_SECONDS=1565190363-: syntax error: operand expected (error token is "-") /usr/share/genkernel/gen_funcs.sh: line 430: let: GK_TIME_RUNTIME_DAYS=/86400: syntax error: operand expected (error token is "/86400") Without --mdadm option genkernel works fine.
Good catch, you hit this because > if isTrue "${CMD_MDADM}" && [ ! -e /sbin/mdadm ] > ^^^^^^^^^^^^^^^^ triggered for you. New beta will land shortly which will contain a fix.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/genkernel.git/commit/?id=70de004ed8550d2c1f9b81140659fee005c2b33f commit 70de004ed8550d2c1f9b81140659fee005c2b33f Author: Thomas Deutschmann <whissi@gentoo.org> AuthorDate: 2019-08-07 15:38:10 +0000 Commit: Thomas Deutschmann <whissi@gentoo.org> CommitDate: 2019-08-07 15:45:19 +0000 gen_cmdline.sh: parse_cmdline(): We no longer require /sbin/mdadm to be present on host system In addition, this will remove an invalid call to print_warning. Bug: https://bugs.gentoo.org/691686 Signed-off-by: Thomas Deutschmann <whissi@gentoo.org> gen_cmdline.sh | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-)
Fix is in >=sys-kernel/genkernel-4.0.0_beta11, thank you for the report!
