Jürg Billeter wrote: > I've also run a script to find used kernel headers over the sources of > the 800 packages (except kernel and headers packages). You can find the > results on http://www.paldo.org/headers/
Wow. Again, excellent work. > * headers-list: Sorted list of all found header references > * headers-xref: Header list cross-referenced to the package names > (useful to exclude header references of kernel module source code that's > unfortunately part of some userspace tarballs) > * linux-glibc-headers-list: List of files installed by my header script > * linux-glibc-headers-diff: diff between headers-list and > linux-glibc-headers-list So if I understand the results correctly, headers-list is the result of grepping all the sources. Hmmm, clearly this is not a foolproof list because a header might not actually be required even tho' it appears in a source file somewhere (due to configure checks, preprocessor conditionals etc). I s'pose the only foolproof way would be to somehow save the header dependency info (gcc -M) from actual compilation (a la Glibc) and use that as the data source. I guess this explains why some headers are cross-referenced even tho' your script doesn't install them eg: linux/init.h. Grepping for that header in grub, e2fsprogs and gpm indeed shows why it is not required during compilation. Any chance your up-to-date scripts could be made easily accessible somewhere? Thanks. Regards Greg -- http://www.diy-linux.org/ -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
