Re: [suggestion] new target GTAGS.
> Here is what I'm adding: > > ## Support `Global' tags. > GTAGS: > here=`cd $(top_builddir) && pwd` && cd $(top_srcdir) && gtags -i $$ here All right. Thank you. > >> By the way, where does automake put tag files to? > > It puts them in the build directory. > This might be the same as the source directory, if the user chose to > configure in the source tree. In BSD system, '/usr/obj' + is used for build directory. (from now on, I say it 'obj' directory.) % cd /home/owner/prog % make obj <= make 'obj' directory /usr/obj/home/owner/prog created for /home/owner/prog % make cc -O -pipe -Wall -I/home/owner/prog -c /home/owner/prog/main.c ... % ls *.o ls: No match. <= source directory is read only. % cd /usr/obj/home/owner/prog % ls *.o main.o ...<= *.o files are wrtten in 'obj' directory. ... To support BSD build system, global locate tag files not only in source directory but also in 'obj' directory. % cd /home/owner/prog % make obj <= make 'obj' directory % gtags /usr/obj/home/owner/prog<= write tag files in 'obj' % ls G*directory. ls: No match. % global -x main main 83 main.cmain(argc, argv) % cd /usr/obj/home/owner/prog % ls G* GPATH GRTAGS GSYMS GTAGS If there is a convention in automake, I can support it. -- Shigio Yamaguchi - Tama Communications Corporation Mail: [EMAIL PROTECTED], (Spare mail: [EMAIL PROTECTED])
Re: [suggestion] new target GTAGS.
> ">" == Shigio Yamaguchi <[EMAIL PROTECTED]> writes: >> Yes, it does. The following command line makes tag files in >> /var/obj instead of current directory. >> % gtags /var/obj Thanks. >> But gtags must be invoked in the root of source directory. Here is what I'm adding: ## Support `Global' tags. GTAGS: here=`cd $(top_builddir) && pwd` && cd $(top_srcdir) && gtags -i $$here >> By the way, where does automake put tag files to? It puts them in the build directory. This might be the same as the source directory, if the user chose to configure in the source tree. Tom
Re: [PATCH] etags support
> "Derek" == Derek R Price <[EMAIL PROTECTED]> writes: Derek> I added rudimentary support for different implementations of Derek> etags (read the one Automake expects and Exuberent etags) since Derek> they take slightly different options. Exuberent etags is the Derek> version distributed with RedHat Linux 6.2 & I believe Debian Derek> and a few others. Hmm. I'm running RH 6.2 and /usr/bin/etags is the GNU version: creche. etags --version etags (GNU Emacs 20.5) Copyright (C) 1996 Free Software Foundation, Inc. and Ken Arnold This program is distributed under the same terms as Emacs It is pretty lame that the exuberant tags people chose to use the name `etags' for their program. The Emacs etags has been around since 1984 (though maybe it wasn't called "etags" until some time later; it definitely was by 1990 though). Surely they could have picked some name that wasn't already in use. I don't mind supporting some other version of tags, but I think it would be easiest if we just introduced a new target. Derek> This was enough to get the TAGS target working with CVS, but Derek> what it probably still needs is a test for support for Derek> "--lang=none" and a hook like @AMDEP@ to comment out the TAGS Derek> target or support in missing for when the user doesn't have Derek> etags installed or configure can't figure out how it works. The `--lang=none' thing is definitely specific to the Emacs etags. That must appear in your Makefile.am though -- meaning that your Makefile.am was written to work with the Emacs etags. This isn't an uncommon practice, either. I don't want to add missing support for etags. tags is a developer's target. If a developer wants to use it, he should (1) know what etags is, and (2) have it installed. Adding configure machinery for this seems like overkill. It's true that we do this for the C compiler, but the situations aren't really analogous. Tom
Re: Automake suffixes ordering [patch]
> "Kevin" == Kevin Ryde <[EMAIL PROTECTED]> writes: Kevin> I find though that I got it wrong for the case where automake Kevin> isn't automatically generating any suffixes, but rather there's Kevin> only user-supplied ones with $(SUFFIXES). This comes up in Kevin> autoconf I think. Thanks. I'm checking in your patch. Kevin> The one liner below is the amendment. If it can't be Kevin> considered part of the original change, then a log entry might Kevin> be, Every change needs a log entry. Here's what I ended up using: 2000-12-21 Kevin Ryde <[EMAIL PROTECTED]> * automake.in (handle_footer): Generate .SUFFIXES target when user defines suffixes but automake does not. Tom
Re: [PATCH] Re: vtexi.test failing
Derek> Whoops. Forgot to put [PATCH] in the subject line. Don't worry too much about that convention. Anyway, I already checked in a slightly different fix for the bug. Tom
Re: New version of RPMs
"Derek R. Price" wrote: > "Derek R. Price" wrote: > > > I added the etags support to my RPMs: > > I regenerated them again using todays version of the CVS Automake since the > failing vtexi.test wasn't a bug. And one more try. etags.m4 wasn't being installed re my recent email. Regenerated. http://alumni.engin.umich.edu/~oberon/automake-1.4a-0_CVSHome_org_7.noarch.rpm http://alumni.engin.umich.edu/~oberon/automake-1.4a-0_CVSHome_org_7.src.rpm Derek -- Derek Price CVS Solutions Architect ( http://CVSHome.org ) mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com ) -- I will not prescribe medication. I will not prescribe medication. I will not prescribe medication... - Bart Simpson on chalkboard, _The Simpsons_
Re: [PATCH] etags support
"Derek R. Price" wrote:
> > > I added a macro to test for the presence of etags and whether it
> > > supports "--etags-include=" or "-i " for includes.
Okay, one more try. I hadn't added etags.m4 to the Makefile.am so it wasn't being
installed and I also tweaked the AM_PROG_ETAGS macro to call
AM_MISSING_PROG(ETAGS, etags) when it can't find a working version of etags.
I'm including the entire new patch.
Derek
--
Derek Price CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
--
106. Charlie was a Chemist, but Charlie is no more.
What Charlie thought was H20 was H2SO4.
Index: ChangeLog
===
RCS file: /cvs/automake/automake/ChangeLog,v
retrieving revision 1.916
diff -u -r1.916 ChangeLog
--- ChangeLog 2000/12/21 06:07:14 1.916
+++ ChangeLog 2000/12/21 18:07:02
@@ -1,3 +1,10 @@
+2000-12-21 Derek Price <[EMAIL PROTECTED]>
+
+ * m4/etags.m4: Discover the etags implementation
+ * m4/init.m4: Require AM_PROG_ETAGS
+ * tags.am: add support for AM_PROG_ETAGS & don't assume
+ @CONFIG@ is present in the build directory
+
2000-12-20 Marc Espie <[EMAIL PROTECTED]>
* automake.in (handle_texinfo): Make path of $vtexi explicit in
Index: tags.am
===
RCS file: /cvs/automake/automake/tags.am,v
retrieving revision 1.24
diff -u -r1.24 tags.am
--- tags.am 2000/10/16 09:01:36 1.24
+++ tags.am 2000/12/21 18:07:02
@@ -36,17 +36,17 @@
SUBDIRSlist='$(SUBDIRS)'; for subdir in $$list; do \
## Do nothing if we're trying to look in `.'.
SUBDIRS if test "$$subdir" = .; then :; else \
-SUBDIRStest -f $$subdir/TAGS && tags="$$tags -i $$here/$$subdir/TAGS"; \
+SUBDIRStest -f $$subdir/TAGS && tags="$$tags
+$(ETAGS_INCLUDE_OPTION)$$here/$$subdir/TAGS"; \
SUBDIRS fi; \
SUBDIRSdone; \
## Make sure the list of sources is unique.
list='$(SOURCES) $(HEADERS) $(TAGS_FILES)'; \
- unique=`for i in $$list; do \
+ unique=`for i in $$list @CONFIG@; do \
## Handle VPATH correctly.
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | \
$(AWK) '{ files[$$0] = 1; } \
END { for (i in files) print i; }'`; \
## Make sure we have something to run etags on.
- test -z "$(ETAGS_ARGS)@CONFIG@$$unique$(LISP)$$tags" \
- || etags $(ETAGS_ARGS) $$tags @CONFIG@ $$unique $(LISP)
+ test -z "$(ETAGS_ARGS)$$unique$(LISP)$$tags" \
+ || $(ETAGS) $(ETAGS_ARGS) $$tags $$unique $(LISP)
Index: m4/init.m4
===
RCS file: /cvs/automake/automake/m4/init.m4,v
retrieving revision 1.20
diff -u -r1.20 m4/init.m4
--- m4/init.m4 2000/10/10 00:18:52 1.20
+++ m4/init.m4 2000/12/21 18:07:02
@@ -54,6 +54,7 @@
# some platforms.
AC_REQUIRE([AC_PROG_AWK])dnl
AC_REQUIRE([AC_PROG_MAKE_SET])dnl
+AC_REQUIRE([AM_PROG_ETAGS])
AC_REQUIRE([AM_DEP_TRACK])dnl
AC_REQUIRE([AM_SET_DEPDIR])dnl
AC_PROVIDE_IFELSE([AC_PROG_CC],
Index: tests/ChangeLog
===
RCS file: /cvs/automake/automake/tests/ChangeLog,v
retrieving revision 1.309
diff -u -r1.309 tests/ChangeLog
--- tests/ChangeLog 2000/12/17 21:32:57 1.309
+++ tests/ChangeLog 2000/12/21 18:07:02
@@ -1,3 +1,8 @@
+2000-12-21 Derek Price <[EMAIL PROTECTED]>
+
+ * etags.test: New file
+ * Makefile.am (TESTS): added etags.test
+
2000-12-17 Tom Tromey <[EMAIL PROTECTED]>
* Makefile.am (XFAIL_TESTS): Don't mention ldflags.test.
Index: tests/Makefile.am
===
RCS file: /cvs/automake/automake/tests/Makefile.am,v
retrieving revision 1.240
diff -u -r1.240 tests/Makefile.am
--- tests/Makefile.am 2000/12/17 21:32:57 1.240
+++ tests/Makefile.am 2000/12/21 18:07:02
@@ -97,6 +98,7 @@
empty3.test \
empty4.test \
error.test \
+etags.test \
exdir.test \
exdir2.test \
exsource.test \
--- /dev/null Thu Aug 24 05:00:32 2000
+++ tests/etags.testWed Dec 20 19:24:26 2000
@@ -0,0 +1,28 @@
+#! /bin/sh
+
+# Test to make sure depcomp is installed and found properly
+# when required for multiple directories
+
+. $srcdir/defs || exit 1
+
+cat > configure.in << 'END'
+AC_INIT(Makefile.am)
+AM_INIT_AUTOMAKE(nonesuch, nonesuch)
+AM_PROG_ETAGS
+AC_OUTPUT(Makefile)
+END
+
+: > Makefile.am
+
+# Fail gracefully if no autoconf.
+(autoconf --version) > /dev/null 2>&1 || exit 77
+
+$ACLOCAL || exit 1
+autoconf || exit 1
+$AUTOMAKE || exit 1
+./configure || exit 1
+
+egrep '^ETAGS = ..*$' Makefile >/dev/null 2>&1 || exit 1
+egrep '^ETAGS_INCLUDE_OPTION = ..*$' Makefile >/dev/null 2>&1 || exit 1
+
+exit 0
Index: m4/Makefile.am
===
RCS file:
Re: [PATCH] etags support
Raja R Harinath wrote: > > I added a macro to test for the presence of etags and whether it > > supports "--etags-include=" or "-i " for includes. > > If Exuberent etags is supposed to be a drop-in replacement for Emacs > etags, it should support the same options. Otherwise, it is a bug in > the distribution if it gives you a "non-standard" etags (you can call > the Emacs etags the "standard"). Well, there is a precedent in the support for different compiler options and I don't want to waste the time of potential CVS developers because they couldn't get their TAGS file built. A lot of CVS users are installing on RedHat Linux at the moment. Derek -- Derek Price CVS Solutions Architect ( http://CVSHome.org ) mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com ) -- Were it left for me to decide whether we should have a government without newspapers, or newspapers without a government, I should not hesitate a moment to prefer the latter. - Thomas Jefferson (appeared http://hotwired.lycos.com/special/lawsuit/ )
Re: [PATCH] etags support
Hi, "Derek R. Price" <[EMAIL PROTECTED]> writes: > I added rudimentary support for different implementations of etags (read > the one Automake expects and Exuberent etags) since they take slightly > different options. Exuberent etags is the version distributed with > RedHat Linux 6.2 & I believe Debian and a few others. > > What version of etags was Automake expecting and where can I get it? I guess it expects to find the version that's distributed as part of Emacs. > I added a macro to test for the presence of etags and whether it > supports "--etags-include=" or "-i " for includes. If Exuberent etags is supposed to be a drop-in replacement for Emacs etags, it should support the same options. Otherwise, it is a bug in the distribution if it gives you a "non-standard" etags (you can call the Emacs etags the "standard"). - Hari -- Raja R Harinath -- [EMAIL PROTECTED] "When all else fails, read the instructions." -- Cahn's Axiom "Our policy is, when in doubt, do the right thing." -- Roy L Ash
Re: New version of RPMs
"Derek R. Price" wrote: > I added the etags support to my RPMs: I regenerated them again using todays version of the CVS Automake since the failing vtexi.test wasn't a bug. http://alumni.engin.umich.edu/~oberon/automake-1.4a-0_CVSHome_org_6.noarch.rpm http://alumni.engin.umich.edu/~oberon/automake-1.4a-0_CVSHome_org_6.src.rpm Derek -- Derek Price CVS Solutions Architect ( http://CVSHome.org ) mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com ) -- Of liberty I would say that, in the whole plenitude of its extent, it is unobstructed action according to our will. But rightful liberty is unobstructed action according to our will within limits drawn around us by the equal rights of others. I do not add 'within the limits of the law,' because law is often but the tyrant's will, and always so when it violates the right of an individual. - Thomas Jefferson to I. Tiffany, 1819.
[PATCH] Re: vtexi.test failing
"Derek R. Price" wrote: > "Derek R. Price" wrote: > > > vtexi.test is failing in the CVS automake. I assume it broke due to the > > recent vtexi behavior change. > > I just looked and I was right. The fix was simple - the test simply wasn't > expecting the $(srcdir)/ prefix on version.texi. Whoops. Forgot to put [PATCH] in the subject line. Derek -- Derek Price CVS Solutions Architect ( http://CVSHome.org ) mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com ) -- This score just in: OS/2, Windows 95, LinuxPPC 2000. Index: vtexi.test === RCS file: /cvs/automake/automake/tests/vtexi.test,v retrieving revision 1.4 diff -u -r1.4 vtexi.test --- vtexi.test 1997/02/23 19:41:20 1.4 +++ vtexi.test 2000/12/21 20:54:44 @@ -24,4 +24,4 @@ $AUTOMAKE || exit 1 -grep '^textutils\.info: textutils\.texi version\.texi$' Makefile.in +grep '^textutils\.info: textutils\.texi $(srcdir)/version\.texi$' Makefile.in
Re: vtexi.test failing
"Derek R. Price" wrote: > vtexi.test is failing in the CVS automake. I assume it broke due to the > recent vtexi behavior change. I just looked and I was right. The fix was simple - the test simply wasn't expecting the $(srcdir)/ prefix on version.texi. Derek -- Derek Price CVS Solutions Architect ( http://CVSHome.org ) mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com ) -- This score just in: OS/2, Windows 95, LinuxPPC 2000. Index: vtexi.test === RCS file: /cvs/automake/automake/tests/vtexi.test,v retrieving revision 1.4 diff -u -r1.4 vtexi.test --- vtexi.test 1997/02/23 19:41:20 1.4 +++ vtexi.test 2000/12/21 20:54:44 @@ -24,4 +24,4 @@ $AUTOMAKE || exit 1 -grep '^textutils\.info: textutils\.texi version\.texi$' Makefile.in +grep '^textutils\.info: textutils\.texi $(srcdir)/version\.texi$' Makefile.in
Improve your stepfamily life
Does your stepfamily life resemble a soap opera more than it does the Brady Bunch? The Stepfamily Association of America invites you to participate in THE NATIONAL CONFERENCE FOR STEPFAMILIES, Feb. 23-24, 2001, at the New Orleans Marriott Hotel. This is an opportunity, designed by knowledgeable professionals, in stepfamilies themselves, to help you: * Make your remarriage a success * Create bonds with your stepchildren * Help your children adjust emotionally * Manage money matters unique to your family * Get more help from legal, financial, psychological advisors * Overcome stepfather and stepmother stereotypes * Elicit cooperation from your children's schools * Bring more harmony into family life Complete conference details at http://www.edupr.com REGISTER ONLINE! Attend, and also enjoy Mardi Gras week in New Orleans! Special discounts for couples, students, groups. HOTEL IS BOOKING UP FAST. ACT NOW BEFORE ROOM BLOCK AND AIRLINE SEATS FILL Special rates for conference attendees. Visit http://www.edupr.com for discounts. Childcare available through a bonded local service. Up to 17 professional development credits available if you are an educator, clinician, financial planner, social worker. Questions? Email [EMAIL PROTECTED] If you would like to be removed, please email us back with the word "Remove" in the subject line. We apologize for any inconvenience.
Improve your stepfamily life
Does your stepfamily life resemble a soap opera more than it does the Brady Bunch? The Stepfamily Association of America invites you to participate in THE NATIONAL CONFERENCE FOR STEPFAMILIES, Feb. 23-24, 2001, at the New Orleans Marriott Hotel. This is an opportunity, designed by knowledgeable professionals, in stepfamilies themselves, to help you: * Make your remarriage a success * Create bonds with your stepchildren * Help your children adjust emotionally * Manage money matters unique to your family * Get more help from legal, financial, psychological advisors * Overcome stepfather and stepmother stereotypes * Elicit cooperation from your children's schools * Bring more harmony into family life Complete conference details at http://www.edupr.com REGISTER ONLINE! Attend, and also enjoy Mardi Gras week in New Orleans! Special discounts for couples, students, groups. HOTEL IS BOOKING UP FAST. ACT NOW BEFORE ROOM BLOCK AND AIRLINE SEATS FILL Special rates for conference attendees. Visit http://www.edupr.com for discounts. Childcare available through a bonded local service. Up to 17 professional development credits available if you are an educator, clinician, financial planner, social worker. Questions? Email [EMAIL PROTECTED] If you would like to be removed, please email us back with the word "Remove" in the subject line. We apologize for any inconvenience.
Re: Automake suffixes ordering [patch]
Tom Tromey <[EMAIL PROTECTED]> writes:
>
> Thanks, I finally checked this in.
Excellent.
I find though that I got it wrong for the case where automake isn't
automatically generating any suffixes, but rather there's only
user-supplied ones with $(SUFFIXES). This comes up in autoconf I
think.
The one liner below is the amendment. If it can't be considered part
of the original change, then a log entry might be,
* automake.in (handle_footer): Correction to last change, for
case where there's no automake suffixes only user $(SUFFIXES).
Index: automake.in
===
RCS file: /cvs/automake/automake/automake.in,v
retrieving revision 1.808
diff -u -r1.808 automake.in
--- automake.in 2000/12/21 06:07:14 1.808
+++ automake.in 2000/12/21 20:06:35
@@ -3661,7 +3661,7 @@
# before .SUFFIXES. So we make sure that .SUFFIXES appears before
# anything else, by sticking it right after the default: target.
$output_header .= ".SUFFIXES:\n";
-if (@suffixes)
+if (@suffixes || &variable_defined ('SUFFIXES'))
{
# Make sure suffixes has unique elements. Sort them to ensure
New version of RPMs
I added the etags support to my RPMs: http://alumni.engin.umich.edu/~oberon/automake-1.4a-0_CVSHome_org_5.src.rpm http://alumni.engin.umich.edu/~oberon/automake-1.4a-0_CVSHome_org_5.src.rpm Derek -- Derek Price CVS Solutions Architect ( http://CVSHome.org ) mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com ) -- He always has. - Humphrey Bogart as Rick, _Casablanca_
[PATCH] etags support
I added rudimentary support for different implementations of etags (read
the one Automake expects and Exuberent etags) since they take slightly
different options. Exuberent etags is the version distributed with
RedHat Linux 6.2 & I believe Debian and a few others.
I added a macro to test for the presence of etags and whether it
supports "--etags-include=" or "-i " for includes.
This was enough to get the TAGS target working with CVS, but what it
probably still needs is a test for support for "--lang=none" and a hook
like @AMDEP@ to comment out the TAGS target or support in missing for
when the user doesn't have etags installed or configure can't figure out
how it works.
What version of etags was Automake expecting and where can I get it?
Derek
--
Derek Price CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
--
There are two major products to come out of Berkley: LSD and UNIX . We don't
believe this to be a coincidence.
Index: ChangeLog
===
RCS file: /cvs/automake/automake/ChangeLog,v
retrieving revision 1.916
diff -u -r1.916 ChangeLog
--- ChangeLog 2000/12/21 06:07:14 1.916
+++ ChangeLog 2000/12/21 18:07:02
@@ -1,3 +1,10 @@
+2000-12-21 Derek Price <[EMAIL PROTECTED]>
+
+ * m4/etags.m4: Discover the etags implementation
+ * m4/init.m4: Require AM_PROG_ETAGS
+ * tags.am: add support for AM_PROG_ETAGS & don't assume
+ @CONFIG@ is present in the build directory
+
2000-12-18 Tom Tromey <[EMAIL PROTECTED]>
* automake.in (handle_built_sources): Removed.
Index: tags.am
===
RCS file: /cvs/automake/automake/tags.am,v
retrieving revision 1.24
diff -u -r1.24 tags.am
--- tags.am 2000/10/16 09:01:36 1.24
+++ tags.am 2000/12/21 18:07:02
@@ -36,17 +36,17 @@
SUBDIRSlist='$(SUBDIRS)'; for subdir in $$list; do \
## Do nothing if we're trying to look in `.'.
SUBDIRS if test "$$subdir" = .; then :; else \
-SUBDIRStest -f $$subdir/TAGS && tags="$$tags -i $$here/$$subdir/TAGS"; \
+SUBDIRStest -f $$subdir/TAGS && tags="$$tags
+$(ETAGS_INCLUDE_OPTION)$$here/$$subdir/TAGS"; \
SUBDIRS fi; \
SUBDIRSdone; \
## Make sure the list of sources is unique.
list='$(SOURCES) $(HEADERS) $(TAGS_FILES)'; \
- unique=`for i in $$list; do \
+ unique=`for i in $$list @CONFIG@; do \
## Handle VPATH correctly.
if test -f "$$i"; then echo $$i; else echo $(srcdir)/$$i; fi; \
done | \
$(AWK) '{ files[$$0] = 1; } \
END { for (i in files) print i; }'`; \
## Make sure we have something to run etags on.
- test -z "$(ETAGS_ARGS)@CONFIG@$$unique$(LISP)$$tags" \
- || etags $(ETAGS_ARGS) $$tags @CONFIG@ $$unique $(LISP)
+ test -z "$(ETAGS_ARGS)$$unique$(LISP)$$tags" \
+ || $(ETAGS) $(ETAGS_ARGS) $$tags $$unique $(LISP)
Index: m4/init.m4
===
RCS file: /cvs/automake/automake/m4/init.m4,v
retrieving revision 1.20
diff -u -r1.20 m4/init.m4
--- m4/init.m4 2000/10/10 00:18:52 1.20
+++ m4/init.m4 2000/12/21 18:07:02
@@ -54,6 +54,7 @@
# some platforms.
AC_REQUIRE([AC_PROG_AWK])dnl
AC_REQUIRE([AC_PROG_MAKE_SET])dnl
+AC_REQUIRE([AM_PROG_ETAGS])
AC_REQUIRE([AM_DEP_TRACK])dnl
AC_REQUIRE([AM_SET_DEPDIR])dnl
AC_PROVIDE_IFELSE([AC_PROG_CC],
Index: tests/ChangeLog
===
RCS file: /cvs/automake/automake/tests/ChangeLog,v
retrieving revision 1.309
diff -u -r1.309 tests/ChangeLog
--- tests/ChangeLog 2000/12/17 21:32:57 1.309
+++ tests/ChangeLog 2000/12/21 18:07:02
@@ -1,3 +1,8 @@
+2000-12-21 Derek Price <[EMAIL PROTECTED]>
+
+ * etags.test: New file
+ * Makefile.am (TESTS): added etags.test
+
2000-12-17 Tom Tromey <[EMAIL PROTECTED]>
* Makefile.am (XFAIL_TESTS): Don't mention ldflags.test.
Index: tests/Makefile.am
===
RCS file: /cvs/automake/automake/tests/Makefile.am,v
retrieving revision 1.240
diff -u -r1.240 tests/Makefile.am
--- tests/Makefile.am 2000/12/17 21:32:57 1.240
+++ tests/Makefile.am 2000/12/21 18:07:02
@@ -97,6 +98,7 @@
empty3.test \
empty4.test \
error.test \
+etags.test \
exdir.test \
exdir2.test \
exsource.test \
--- /dev/null Thu Aug 24 05:00:32 2000
+++ m4/etags.m4 Thu Dec 21 12:03:24 2000
@@ -0,0 +1,60 @@
+#
+# Find some information about the etags program
+#
+# Sets
+# ETAGS = path to etags
+# ETAGS_INCLUDE_OPTION = option to pass to etags with arg for includes
+#
+
+AC_DEFUN([AM_PROG_ETAGS],
+[AC_BEFORE([$0], AM_PROG_ETAGS_WORKS)
+AC_CHECK_PROG(ETAGS, etags, etags)
+if test -z "$ETAGS"; then
+ AC_CHECK_PROG(ETAGS, ctags, ctags -e)
+fi
+if test -n "$ETAGS"; then
+
vtexi.test failing
vtexi.test is failing in the CVS automake. I assume it broke due to the recent vtexi behavior change. Derek -- Derek Price CVS Solutions Architect ( http://CVSHome.org ) mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com ) -- [Let us] go on in doing with [the] pen what in other times was done with the sword, [and] show that reformation is more practicable by operating on the mind than on the body of man. - Thomas Jefferson to Thomas Paine, 1792
Re: ./configure & .deps directory
Tom Tromey wrote: > > "Derek" == Derek R Price <[EMAIL PROTECTED]> writes: > > Derek> Is there a good reason the configure script creates > Derek> $(top_builddir)/.deps during the test that sets $DEPDIR and > Derek> doesn't delete it again? Besides some developer or other > Derek> needing sleep? ;) > > Derek> My distribution certainly doesn't seem to need that directory > Derek> sitting around... > > This directory is needed by the dependency tracking implementation. > > I agree though that this macro is mysterious. Why doesn't it create > `_deps' if that is what is chosen? What's $(top_builddir)/.deps get used for when there aren't any C sources in $(top_srcdir) or $(top_builddir)? Derek -- Derek Price CVS Solutions Architect ( http://CVSHome.org ) mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com ) -- One woman has hurt you and you'll take it out on the rest of the world? You're a coward and a weakling! - Ingrid Bergman as Elsa, _Casablanca_
Snowhite and the Seven Dwarfs - The REAL story!
Today, Snowhite was turning 18. The 7 Dwarfs always where very educated and polite with Snowhite. When they go out work at mornign, they promissed a *huge* surprise. Snowhite was anxious. Suddlently, the door open, and the Seven Dwarfs enter... sexy virgin.scr
