From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com
Cc: gdb@sources.redhat.com
Subject: Re: DejaGNU vs snapshots [drow@mvista.com: Re: [5.3] What's the hold up?]
Date: Mon, 03 Mar 2003 20:50:00 -0000 [thread overview]
Message-ID: <200303032050.h23KoP830562@duracef.shout.net> (raw)
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
next reply other threads:[~2003-03-03 20:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 20:50 Michael Elizabeth Chastain [this message]
2003-03-03 20:55 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2003-03-03 20:00 Michael Elizabeth Chastain
2003-03-03 20:05 ` Daniel Jacobowitz
2003-03-03 14:47 Michael Elizabeth Chastain
2003-03-03 3:55 Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200303032050.h23KoP830562@duracef.shout.net \
--to=mec@shout.net \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox