From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com, 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 14:47:00 -0000 [thread overview]
Message-ID: <200303031447.h23ElRc25240@duracef.shout.net> (raw)
Yeah, that's the same problem (PR gdb/708), and the same patch that
I have: add a distclean-local goal to Makefile.am.
I am working on this as a prospective dejagnu contributor now,
so I want to dig a little deeper. dejagnu has a lot of crap in
their configure/automake/make-distribution logic, such as a
custom TCL script to do cleaning!
My plan is to cuddle up with the autoconf/automake/libtool book
and then clean up CVS dejagnu and then do an import. We can do
something faster in sourceware if we want, either the 'distclean-local'
idea or Andrew's earlier local fix from 2000, which is even simpler:
add 'example' and 'testsuite' to the SUBDIRS list in Makefile.am.
Michael C
next reply other threads:[~2003-03-03 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 14:47 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-03 20:50 Michael Elizabeth Chastain
2003-03-03 20:55 ` Daniel Jacobowitz
2003-03-03 20:00 Michael Elizabeth Chastain
2003-03-03 20:05 ` Daniel Jacobowitz
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=200303031447.h23ElRc25240@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