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 20:00:00 -0000 [thread overview]
Message-ID: <200303032000.h23K0SA29771@duracef.shout.net> (raw)
About this patch for the dejagnu droppings:
--- src/dejagnu/Makefile.am 2002-04-21 04:46:47.000000000 -0400
+++ tsrc/dejagnu/Makefile.am 2002-11-20 16:35:17.000000000 -0500
@@ -34,10 +34,13 @@
# We don't use SUBDIRS, so the excample or test cases don't get built
# by default for a "make all".
clean-local:
- cd doc ; $(MAKE) clean
cd testsuite ; $(MAKE) clean
cd example ; $(MAKE) clean
+distclean-local:
+ cd testsuite ; $(MAKE) distclean
+ cd example ; $(MAKE) distclean
+
I started down this path, but it needs more work. The problem is
that dejagnu/example/calc/Makefile.in does not remove config.status
when it does a distclean. I tried regenerating this file from
dejagnu/example/calc/Makefile.am, but various versions of automake
gave me attitude in various ways.
Now my plan is:
(1) read the autoconf/automake/libtool book
(2) do a big cleanup in cvs dejagnu
(3) import to sourceware
But that's going to take a while, so I'm going to fall back and do
something cheap so that our tarballs work. Probably revive this patch:
revision 1.2
date: 2000/04/19 02:28:55; author: cagney; state: Exp; lines: +1 -1
Add directory example to SUBDIRS.
That worked for two years and then got overwritten by an import.
Michael C
next reply other threads:[~2003-03-03 20:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 20:00 Michael Elizabeth Chastain [this message]
2003-03-03 20:05 ` Daniel Jacobowitz
-- 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 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=200303032000.h23K0SA29771@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