Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 24 Jan 2003 12:14:54 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 24 Jan 2003 12:14:54 -0500 Received: from air-2.osdl.org ([65.172.181.6]:56496 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id ; Fri, 24 Jan 2003 12:14:52 -0500 Date: Fri, 24 Jan 2003 09:18:25 -0800 (PST) From: "Randy.Dunlap" X-X-Sender: To: cc: Subject: Re: test suite? In-Reply-To: <1043426077.1620.10.camel@localhost.localdomain> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org | From: Robert P. J. Day | | i've noticed references to "test suites" for kernels, but | is there any one-step convenient way to select every possible | option for test-compiling a new kernel, just to see if it builds? | perhaps an "everything" option? | | and, related to that, should such a kernel theoretically | work? as in, are there any options that would be mutually | exclusive that would cause such a build to fail? | | still thinking about reorganizing the overall option structure, Hi, I notice that you've already had a reply on this (use "make help", "make allmodconfig" or "make allyesconfig" etc.). OSDL's PLM does this (make allmodconfig) for each new (2.5) kernel release and the results are posted at http://www.osdl.org/archive/cherry/stability/ and also in the PLM web page interface. The script that is used for this is at that same URL above. PLM is at http://www.osdl.org/cgi-bin/plm/ . Has anyone tried to boot an 'allyesconfig' kernel? I'll give that a shot now. HTH. -- ~Randy - 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/