> (Generic 2.4.18 include/linux/mm.h)
> extern int do_munmap(struct mm_struct *, unsigned long, size_t);
> (RH 7.3/AC patched 2.4.18-3 include/linux/mm.h)
> extern int do_munmap(struct mm_struct *, unsigned long, size_t, int
> My question is what is the recommended way for module developers to
> handle changes to this API so that end users don't have to edit
> makefiles to build for their particular kernel? Is there a way to
Add some tests in a ./configure script that finds out which one
is being used in the kernel headers.
> how to handle this besides grep'ing source in my installer? :-)
It's roughly similar to this though. API creep is one of the facts of
external module development on Linux, I'm afraid.
-- "Do you mean to tell me that "The Prince" is not the set textbook for CS1072 Professional Issues ? What on earth do you learn in that course ?" - David Lester - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/