On Sam, 2006-03-18 at 08:50 +1100, Greg Schafer wrote: > Jürg Billeter wrote: > > * 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.
Yes, that's unfortunately not that easy to do in general except by doing a full distro rebuild with a gcc wrapper script or something similar but I'm not up to do that at the moment. Not really used includes and kernel modules in userspace application tarballs are the two main points why the list is not as useful as it could be. The -xref list might save some time when checking header files, though. > Any chance your up-to-date scripts could be made easily accessible > somewhere? Thanks. Sure, I've put linux-glibc-headers-20060317 and header-find-script on http://www.paldo.org/headers/ header-find-script is customized for paldo but it should be easy to adapt it to other environments. Regards, Jürg -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
