Re: [PATCH] etags support

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

Re: [PATCH] etags support

On 21 Dec 2000, Tom Tromey wrote: "Derek" == Derek R Price [EMAIL PROTECTED] writes: 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

Re: [PATCH] etags support

Tom Tromey wrote: "Derek" == Derek R Price [EMAIL PROTECTED] writes: Hmm. I'm running RH 6.2 and /usr/bin/etags is the GNU version: I just looked into it and it looks like etags was distributed with the version of emacs (20.5) that was distributed with RedHat 6.2. They've removed it from

Re: [suggestion] new target GTAGS.

"" == Shigio Yamaguchi [EMAIL PROTECTED] writes: In BSD system, '/usr/obj' + current directory is used for build directory. (from now on, I say it 'obj' directory.) If there is a convention in automake, I can support it. There isn't a simple convention like this. The person building the

Handle Libtool from multi-language-branch

Hi, The following patch adds minimal support for Libtool from the multi-language-branch. Index: automake.in === RCS file: /cvs/automake/automake/automake.in,v retrieving revision 1.810 diff -u -p -u -r1.810 automake.in ---

Re: ./configure .deps directory

Derek What's $(top_builddir)/.deps get used for when there aren't any C Derek sources in $(top_srcdir) or $(top_builddir)? Thanks, I checked in the fix. Tom

distclean-generic bug

The distclean-generic target is removing the following files: stamp-h stamp-h[0-9]* The listing of 'stamp-h[0-9]*' causes 'stamp-h[0-9].in' files to be removed incorrectly. And incidentally, it would be unecessary to list stamp-h if you applied the stamp-h fix I sent to the list sometime

distributing files generated by configure

I have several files which are generated by configure that I want three things to happen to. 1) Created in $(srcdir) rather than $(builddir) or, alternately and second best, targets added which make the $(srcdir) counterparts dependent on the $(builddir) versions. I don't like option 2 because

BSD make and dependencies

Is there any support in Automake for BSD make's style of includes? Apparently BSD wants something like the following: .include file or .include file Where and have similiar meanings to what they would have in a C program include. Derek -- Derek Price CVS

Re: distributing files generated by configure

Hi, Derek R. Price [EMAIL PROTECTED] writes: I have several files which are generated by configure that I want three things to happen to. 1) Created in $(srcdir) Then they shouldn't be created by 'configure' :-) rather than $(builddir) or, alternately and second best, targets added