This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: DejaGNU vs snapshots [drow@mvista.com: Re: [5.3] What's the hold up?]
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: Michael Elizabeth Chastain <mec at shout dot net>
- Cc: gdb at sources dot redhat dot com
- Date: Mon, 3 Mar 2003 15:05:51 -0500
- Subject: Re: DejaGNU vs snapshots [drow@mvista.com: Re: [5.3] What's the hold up?]
- References: <200303032000.h23K0SA29771@duracef.shout.net>
On Mon, Mar 03, 2003 at 02:00:28PM -0600, Michael Elizabeth Chastain wrote:
> 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.
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.
>
> Now my plan is:
>
> (1) read the autoconf/automake/libtool book
> (2) do a big cleanup in cvs dejagnu
> (3) import to sourceware
I don't think a "big" cleanup is called for.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer