From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7070 invoked by alias); 28 Mar 2003 10:36:47 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 7063 invoked from network); 28 Mar 2003 10:36:46 -0000 Received: from unknown (HELO vlsi1.ultra.nyu.edu) (128.122.140.213) by sources.redhat.com with SMTP; 28 Mar 2003 10:36:46 -0000 Received: by vlsi1.ultra.nyu.edu (4.1/1.34) id AA27659; Fri, 28 Mar 03 05:40:37 EST Date: Fri, 28 Mar 2003 11:50:00 -0000 From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner) Message-Id: <10303281040.AA27659@vlsi1.ultra.nyu.edu> To: guerby@acm.org Subject: Re: ACATS & GCC testsuite Cc: gcc@gcc.gnu.org X-SW-Source: 2003-03/txt/msg01704.txt.bz2 I'm not sure why autogen is needed for testing, the only thing you need is dejagnu and then "make -k check" just works. (I have dejagnu-1.4.2-6 on my RedHat 8.0 machine). But you also have to do a full build and doing it in maintainer-mode is best. Those require automake, autogen, and autoheader. > I'm not sure which message you're paraphrasing here, but I'm sure > there must be a miscommunication here. It is of course extremely > valuable if any regressions are caught when they occur! http://gcc.gnu.org/ml/gcc/2003-01/msg01299.html Note that the "total waste of time" was *your* wording, not mine! I was agreeing with it due to the reason Geert gave yesterday: tracking down the ACAS failures most likely will duplicate work already done.