> I would suggest to only work on files that compile. e.g. do a > > make allyesconfig > make -j$[$(grep -c processor /proc/cpuinfo)*2] &1 |tee LOG (will probably take a long time) > > first and then only modify files when are mentioned in "LOG" Actually since this will probably take very long on a slower machine you can refer to http://halobates.de/allyes/ for some allyes buildlogs of recent kernels for i386 and x86-64. A trick to quickly check if something compiles is also to do make allyesconfig make path/to/file.o That won't catch linker errors, but if you don't have warnings there are normally no linker errors either. -Andi - To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
