Re: Build-depends: autoconf, automake ?
On Sun, 26 Nov 2000, Mariusz Przygodzki wrote:
> On Sunday 26 November 2000 20:40, Steve Robbins wrote:
> > 1. Automake inserts a makefile variable "TAR" into every Makefile.in
> > generated. Upstream has "TAR = gtar", but I have "TAR = tar", greatly
> > (and needlessly) inflating the .diff. The value of TAR is hardcoded into
> > automake itself.
>
> I don't believe it. I think a variable "TAR" is defined in Makefile.am.
Well then, I invite you to check out the sources of any automake'ified
package and report back to us.
> > Unfortunately, one of the things run is "aclocal", but without the
> > necessary "-I m4" flag, causing the build to fail. [Amusingly, the build
> > would work if automake was not installed, because the "missing" script
> > will just touch the files to get the timestamps in the right order.]
>
> In this case aclocal needs macros from other *.m4 file than aclocal.m4. These
> additional files *should* be in upstream sources, if not try to contact with
> upstream authors(s).
Yes, the files are present in the upstream source. That is not the
problem. The problem is that automake does not know that I need to
specify a "-I" flag to aclocal when it generates these rules in
Makefile.in.
> You can define it, for example. as "preconfigure" in debian/rules because you
> have to use it just once.
Yes, that is a good idea.
-S
Reply to: