[esr]
> > CML2 would probably reject most random configurations for violating
> > some consistency constraint or other. What kind of errors eould we
> > be hunting, anyway?
[kaos]
> Not raw random configurations, the idea is to generate a random
> config then run it through make oldconfig (CML1) or any CML2 to
> generate a consistent config. Then try to compile and link using
> that config, the aim is to catch broken makefiles or headers,
...or missing constraints in CML2. If a random config fails to
compile, it is probably a problem with headers or makefiles -- but it
*could* be a combination that makes no sense and should not have been
allowed by the config system.
Peter
_______________________________________________
kbuild-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/kbuild-devel
