i used to think i understood how "make headers_install" created the set of sanitized headers, but now i'm not so sure. since you can run that immediately after running "make distclean", the sanitized headers are clearly arch-independent and don't depend on doing any preliminary configuration. but after i run it, as a single example, i can see i have the generated header file "usr/include/asm/page.h". so the obvious question is -- what caused that header file to be added to the sanitized headers? i thought that process was controlled exclusively through the Kbuild* files, and the only Kbuild file that refers to page.h is: $ grep "page\.h" $(find . -name Kbuild*) ./include/asm-frv/Kbuild:unifdef-y += page.h is *that* the cause? if so, why, after i delete that line, do i *still* get page.h being added? what am i misunderstanding here? rday -- ======================================================================== Robert P. J. Day Linux Consulting, Training and Annoying Kernel Pedantry Waterloo, Ontario, CANADA http://fsdev.net/wiki/index.php?title=Main_Page ======================================================================== -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
