Ken Moffat wrote: > I've just noticed that someone on CLFS ran 'make headers_check' and > feared that the usual error reports (from kexec.h and soundcard.h) > about "userspace cannot reference function or variable defined in the > kernel" were errors. > > In theory, running "make headers_check" allows _kernel_ devs to > check that they aren't making things worse. In practice, these two > messages have been present for as long as I can remember, without > any userspace problems that are attributable to this, nor any > interest in removing these two messages. > > So, although illustrating the command may have some use if we have > any users who plan to be kernel devs, for a normal builder it appears > to give zero utility. I suspect, as far as the book is concernd, > that it is another of those ideas which seemed like a good idea at > the time, but now serves no purpose. > > Should we just drop this command ?
Perhaps we should. What is happening is that scripts/headers_check.pl is being run. The comments say: # Usage: headers_check.pl dir arch [files...] # dir: dir to look for included files # arch: architecture # files: list of files to check # # The script reads the supplied files line by line and: # # 1) for each include statement it checks if the # included file actually exists. # Only include files located in asm* and linux* are checked. # The rest are assumed to be system include files. # # 2) It is checked that prototypes does not use "extern" # # 3) Check for leaked CONFIG_ symbols Both soundcard.h and kexec.h violate #2. I don't believe these have ever caused a problem and we certainly don't address teh warnings. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
