Created attachment 4526 [details] linux: Choose default kernel configuration depending on the current architecture selected. Hello: I've found out that after initial configuration, including enabling of linux kernel compilation, the default kernel config is not set and almost all make targets fail with: "linux/linux.mk:304: *** No kernel defconfig name specified, check your BR2_LINUX_KERNEL_DEFCONFIG setting." One possible solution would have been tweaking the build system to avoid that message or at least, be able to run the linux-menuconfig target. I didn't find an easy way to do this and therefore I chose another option which is setting kernel default configs depending on target architecture. Find the patch attached, regards,
I believe that the current behavior is the one that we want. The kernel configuration is something that's highly specific to the target hardware, so we can't just chose some arbitrary kernel configuration for each particular architecture. I very much prefer the current behavior in which the user is warned that he should set a kernel configuration, rather than the behavior proposed by the patch, where Buildroot would automatically select some random configuration, the user will not notice, try to boot the kernel on whatever hardware, and see it not boot at all. Also, if we would be doing that for the kernel, we would have to do that for U-Boot and Barebox. And for bootloaders, the fact that we can't decide a good "default" configuration for each particular architecture is well known. The only thing we /might/ do is define the default kernel configuration to be i386 for i386 and x86_64 for x86-64, since those two architectures have only one single kernel defconfigs. But for the other architectures, I don't think it makes sense.