[lkml]   [2003]   [Sep]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Linux 2.6.0-test6
    On Mon, 29 September 2003 19:19:30 +0000, bill davidsen wrote:
    > In article <>,
    > Linus Torvalds <> wrote:
    > | Interesting. I'm pretty sure I did a "make allyesconfig" just before the
    > | test6 release, so apparently x86 includes it indirectly through some path,
    > | and so it only shows up on m68k and arm?
    > |
    > | This, btw, is a pretty common thing. I wonder what we could do to make
    > | sure that different architectures wouldn't have so different include file
    > | structures. It's happened _way_ too often.
    > |
    > | Any ideas?
    > If CPU cycles are no object the include names and order can be picked
    > out of the preprocessor output, add "-E" to the gcc call, pick only the
    > lines starting with "1" and a header name, save in a text file. The
    > problem is that config option (including arch) change the output, so
    > it's only useful as a rough check.

    How is this better than adding "-H", as Jamie suggested?

    > Don't know if this is what you wanted, it does allow the comparison
    > between arch's. Oh, it also shows that some headers are used a lot more
    > than they need be, a few more ifdef's in the low level header files
    > could reduce filesystem thrashing during a build. Some folks have
    > machines which don't keep everything in memory :-(

    How do you find the correct places to prune include lines?


    A defeated army first battles and then seeks victory.
    -- Sun Tzu
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:49    [W:0.020 / U:5.484 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site