Tigran Aivazian wrote:
> a) remove dependency of CONFIG_MICROCODE on CONFIG_DEVS_FS in config.in
> because many users think it is impossible to use microcode driver
> (because devfs is in filesystems section so they have to possess some
> brain to go there and come back to "processor features" - it is better
> to allow it to compile using the standard devfs stubs and then let it
> fail at runtime, next time they will know better and compile devfs)
Run-time reporting of conflicts known at configuration time ? Wow, that's
a concept ! ;-)
You might as well just throw an #error into the code to fail the build.
So at least people will know before they reboot.
Better yet, an error or warn verb in the configuration language might
be quite useful. Or a way to declare forward references, but that approach
has other problems (e.g. how to sneak them into the Configure script).
- Werner
-- _________________________________________________________________________ / Werner Almesberger, ICA, EPFL, CH werner.almesberger@ica.epfl.ch / /_IN_N_032__Tel_+41_21_693_6621__Fax_+41_21_693_6610_____________________/- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Mar 15 2000 - 21:00:17 EST