> Well, see...that's a problem. The ELKS kernel uses a really old copy of > Kconfig from Linux and when I looked at extracting the one used in a more > modern Linux source code base the task was far from trivial. A lot of ELKS > was cobbled together well over a decade ago. I'm open to moving to a more > all-encompassing build system if someone wants to do it, but it certainly > will not be a simple task. Mmm... let us be pragmatic and stop dreaming with stuff like "changing the compiler", "moving to another build system", etc. ELKS is definitively a "hobby" / "educational" project, with a few active contributors, and is intended to have fun, not for business (except data erasing / recovery on antic machines ?). So our development strategy should be consistent with that matter of fact : little steps forward, and keep consistency and stability. Obsolescence is absolutely NOT a concern here, as long we find compatible emulators and embedded systems to play with. Back to the current Kconfig: it works quite well, fulfills the need, so why breaking it with an hazardous upgrade ? I only propose to use it not only for the kernel, but also for the applets and image format selection. Not to upgrade it. MFLD -- To unsubscribe from this list: send the line "unsubscribe linux-8086" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
