Yes, this sounds like very desirable. However, I have experience with
compiling the 4-front intermediate layer. That was quite a hassle, and
it managed to fail in so many ways, that I do NOT expect anybody to
write a foolproof script that will manage to compile a kernel module
in all cases.
The 4-front script would report "something went wrong" when the
desired ".o" file doesn't exist after the compile attempt, which is
not helpful. Sure, it is a microsoft-ism: the user doesn't want to
know. (A friend had a "this device isn't functioning properly" error
on his microsoft machine this weekend. Now how am I supposed to
diagnose that? I guessed IRQ/DMA, slot-dependent conflict, and was
right: swapping cards helped.)
I think it is wrong: The user needs to know the reason why things went
wrong.
Roger.
-- ** R.E.Wolff@BitWizard.nl ** http://www.BitWizard.nl/ ** +31-15-2137555 ** *-- BitWizard writes Linux device drivers for any device you may have! --* * Common sense is the collection of * ****** prejudices acquired by age eighteen. -- Albert Einstein ********- 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/