Re: avoiding target $(srcdir)/Makefile.in

2000-10-02 Thread john heasley
ever mind. i figured out my error in the use of AM_MAINTAINER_MODE. sorry. that should would just fine. thanks. On Mon, Oct 02, 2000 at 03:35:34PM -0700, john heasley darkened my spool with the following: > On Mon, Oct 02, 2000 at 05:02:46AM -0400, Pavel Roskin darkened my spool with the >fo

Re: avoiding target $(srcdir)/Makefile.in

2000-10-02 Thread john heasley
On Mon, Oct 02, 2000 at 05:02:46AM -0400, Pavel Roskin darkened my spool with the following: > Hello, John! > > > is there a macro or option to automake to ommit the target > > for $(srcdir)/Makefile.in, such that it is not necessary to > > include Makefile.am and configure.in in a distribution?

[PATCH] SGI dependency tracking bugfix

2000-10-02 Thread Morten Eriksen
Re-resending this patch. 2000-06-04 Morten Eriksen <[EMAIL PROTECTED]> * depcomp: fixed bug in sgi dependency tracking mode with sourcecode files which does not contain any dependencies to other source files. Regards, Morten Hi, this patch was never applied, so I

[PATCH] compare header files before installing

2000-10-02 Thread Morten Eriksen
Hi, it'd be nice if something like the attached patch could go into Automake. It'd save a lot of recompiling for developers writing libraries. 2000-10-02 Morten Eriksen <[EMAIL PROTECTED]> * header.am (install-@DIR@HEADERS): Don't install a header file if it is identical to th

Re: RFC: Default output destination

2000-10-02 Thread Akim Demaille
| On Mon, Oct 02, 2000 at 05:48:26PM +0200, Akim Demaille wrote: | : (And BTW, why the heck is there this `tab' part?) | | I believe it is short for "table" - the compiler parser is based on using a | state transition table or something along those lines. That's my guess - | I've never used lex

Re: RFC: Default output destination

2000-10-02 Thread Pavel Roskin
Hello, Akim! > which agrees with this behavior. The question is then: did the author > think about file_name=dir_part/base_part? (And BTW, why the heck is > there this `tab' part?) To avoid overriding calc.c if it's a separate source file. > /tmp % ls src *tab* -l

Re: RFC: Default output destination

2000-10-02 Thread Akim Demaille
| Hello, Jim and others! Hi Pavel! | > Is it that behavior documented? The documentation says: With all the source in a single file, you use the following command to convert it into a parser file: @example bison @var{file_name}.y @end example

Re: RFC: Default output destination

2000-10-02 Thread Pavel Roskin
Hello, Jim and others! > Is it that behavior documented? > If so, then it's probably not reasonable to change it. > I've Cc'd the automake list, because some of automake's > rules use bison through $(YACC) -- though I'll bet they > all use it in yacc-compatible mode. Yes, Automake currently used

Re: RFC: Default output destination

2000-10-02 Thread Jim Meyering
Is it that behavior documented? If so, then it's probably not reasonable to change it. I've Cc'd the automake list, because some of automake's rules use bison through $(YACC) -- though I'll bet they all use it in yacc-compatible mode. Akim Demaille <[EMAIL PROTECTED]> writes: | Hi People, | | I c

Re: avoiding target $(srcdir)/Makefile.in

2000-10-02 Thread Pavel Roskin
Hello, John! > is there a macro or option to automake to ommit the target > for $(srcdir)/Makefile.in, such that it is not necessary to > include Makefile.am and configure.in in a distribution? It already becomes a FAQ. Why do you need this? The last person who asked about this alleged that the