From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1454 invoked by alias); 3 Mar 2003 20:50:27 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 1445 invoked from network); 3 Mar 2003 20:50:27 -0000 Received: from unknown (HELO duracef.shout.net) (204.253.184.12) by 172.16.49.205 with SMTP; 3 Mar 2003 20:50:27 -0000 Received: (from mec@localhost) by duracef.shout.net (8.11.6/8.11.6) id h23KoP830562; Mon, 3 Mar 2003 14:50:25 -0600 Date: Mon, 03 Mar 2003 20:50:00 -0000 From: Michael Elizabeth Chastain Message-Id: <200303032050.h23KoP830562@duracef.shout.net> To: drow@mvista.com Subject: Re: DejaGNU vs snapshots [drow@mvista.com: Re: [5.3] What's the hold up?] Cc: gdb@sources.redhat.com X-SW-Source: 2003-03/txt/msg00061.txt.bz2 Hi Daniel, > Try "automake --foreign" in the example/calc/ directory. The version > of automake that I have installed generates a makefile which removes > config.status properly. So does the snapshot from sourceware. > Regenerating it is all it takes. That sounds like it will fix my problem. > I don't think a "big" cleanup is called for. I do. dejagnu currently has a custom *TCL* script to help with the cleanup. There's gotta be some good cleanup opportunities in there. I don't think gdb needs that cleanup to happen, though. It would just be for dejagnu's benefit. Michael C