lkml.org 
[lkml]   [1999]   [Sep]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: "CONFIG_PROCFS" problem in 2.3.18ac8
Matti Aarnio wrote:

> As a side note, job for a aspiring kernel hacker:
>
> In the system (for i386) there are now 565 'CONFIG_.*' entries and
> TWO 'IDEDMA_.*' entries. Scanning the system for such defines which
> are *NOT* defined in any configuration script file would be worthwhile
> job for somebody. Any takers ?
>
> If somebody makes tools to automate such scan, could they, please, be
> published ?

grep CONFIG_ $(find . -type f -a -name '*.[chS]') |
grep ':#if' |
grep -v -F "$(grep ^CONFIG Documentation/Configure.help)" |
awk -F: '{print $2}' |
sort -u

almost does what you want. But there are a lot of CONFIG_ #ifdef's that
never appear in the Configure.help file for i386, so this ends up
producing too much output. If you replaced "$(grep ^CONFIG
Documentation/Configure.help)" with some other way of generating a list,
one per line, of all the CONFIG_ options that you think *are* used, then
the output would be more useful. Also if you got the output down to a
managable amount, you'd probably want to remove the awk and the sort so
that you could see exactly where the problematic #ifdef's are.

alex

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:54    [W:0.028 / U:24.232 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site