I couldn't figure out why the DEFAULT_KERNEL_CONFIG is ignored from genkernel.conf and why I had to manually use --kernel-config every time. So in gen_configkernel.sh, turns out the options are laid out as follows:
determine_config_file() {
for f in
"${CMD_KERNEL_CONFIG}"
"/etc/kernels/kernel-config-${ARCH}-${KV}"
"${GK_SHARE}/arch/${ARCH}/kernel-config-${KV}"
"${GK_SHARE}/arch/${ARCH}/kernel-config-${VER}.${PAT}"
"${GK_SHARE}/arch/${ARCH}/generated-config"
"${GK_SHARE}/arch/${ARCH}/kernel-config"
"${DEFAULT_KERNEL_CONFIG}"
Shouldn't ${DEFAULT_KERNEL_CONFIG} be second on the list, right after ${CMD_KERNEL_CONFIG}? It would make more sense if someone has set it to something in the config, to use that instead of a generated config (which is what mine wanted to do).
I couldn't figure out why the DEFAULT_KERNEL_CONFIG is ignored from genkernel.conf and why I had to manually use --kernel-config every time. So in gen_configkernel.sh, turns out the options are laid out as follows:
determine_config_file() {
for f in
"${CMD_KERNEL_CONFIG}"
"/etc/kernels/kernel-config-${ARCH}-${KV}"
"${GK_SHARE}/arch/${ARCH}/kernel-config-${KV}"
"${GK_SHARE}/arch/${ARCH}/kernel-config-${VER}.${PAT}"
"${GK_SHARE}/arch/${ARCH}/generated-config"
"${GK_SHARE}/arch/${ARCH}/kernel-config"
"${DEFAULT_KERNEL_CONFIG}"
Shouldn't ${DEFAULT_KERNEL_CONFIG} be second on the list, right after ${CMD_KERNEL_CONFIG}? It would make more sense if someone has set it to something in the config, to use that instead of a generated config (which is what mine wanted to do).