On 2/26/06, Diego Calleja <[email protected]> wrote:
> El Sun, 26 Feb 2006 17:21:17 +0100,
> Jesper Juhl <[email protected]> escribió:
>
>
> > 95 kernels were build with 'make randconfig'.
> > 1 kernel was build with the config I normally use for my own box.
> > 1 kernel was build from 'make defconfig'.
> > 1 kernel was build from 'make allmodconfig'.
> > 1 kernel was build from 'make allnoconfig'.
> > 1 kernel was build from 'make allyesconfig'.
>
>
> I wonder if it'd be useful a "make compiletest" which developers
> are told to run before submitting changes - a target that would compile
As a general thing? No, I don't think so. When you've made a change
you generally want to compile test a very specific part of the kernel
(the one containing your change), not the entire kernel.
> a kernel with allyesconfig, another with allnoconfig, allmodconfig
> and a couple of randconfig, with the time it could improve this
> kind of errors.
>
> (I tried to do it myself but I don't know swahili well enought to
> hack Makefiles)
>
No need to hack makefiles, for example, all I did to build my 100
kernels was this simple shell script that I then left to run for a few
hours :
#!/bin/bash
make clean
zcat /proc/config.gz > .config
make oldconfig
cp .config normal.config
make -j 5 2>&1 | tee normal.log
make clean
make defconfig
cp .config def.config
make -j 5 2>&1 | tee def.log
make clean
make allmodconfig
cp .config allmod.config
make -j 5 2>&1 | tee allmod.log
make clean
make allnoconfig
cp .config allno.config
make -j 5 2>&1 | tee allno.log
make clean
make allyesconfig
cp .config allyes.config
make -j 5 2>&1 | tee allyes.log
for i in `seq 1 95`; do make clean ; make randconfig ; cp .config
rand$i.config ; make -j 5 2>&1 | tee rand$i.log ; done
no tricky Makefile hackery there, just a little shell scripting magic.
--
Jesper Juhl <[email protected]>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
