Messages in this thread | | | Date | Sat, 26 Nov 2005 15:19:26 +0100 | From | Pavel Machek <> | Subject | Re: [PATCH] make miniconfig (take 2) |
| |
Hi!
On So 26-11-05 06:25:30, Rob Landley wrote: > On Friday 25 November 2005 20:34, Kyle Moffett wrote: > > I got interested so I started writing a Perl-based replacement that > > actually reads the source config into program memory and writes > > copies out of that RAM each time. > > I did several variants before settling on the one I submitted as "least sucky > for right now". (Starting from zero and adding lines did not work at _all_, > and trying to produce consecutively smaller diffs isn't a winner either. > Anything fancy based on diff runs into the fact that dependencies can enable > stuff _earlier_ in the file, and it's almost impossible to parse. Besides, > diff is noticeably faster when there are few changes, so this was the best > performer of the lot too...) > > And I try to avoid perl dependencies in the linux build process. When you do > cross-compiles that make a minimal toolchain (ala the Linux From Scratch > "/tools" directory) and then chroot into it to create the new system, having > to add perl to the mess is a disproprotionate hassle.
I'd say "don't worry about that, yet".
> Also, zappable lines tend to clump, so if it gets 2 zappable lines in a row it > could speculatively try zapping 2 at a time to see if it makes faster > progress. (The down side is the extra allnoconfig runs for backing up and > iterating through on failures to see _which_ ones made a difference. That's > not low-hanging fruit, may not be edible at all...)
Can't you just filter out all the comments beforehand? Pavel -- Thanks, Sharp! - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |