Hello!
[Wed, 24 Mar 2004] Jack O'Quin wrote:
> They should be, and they usually are, but it's not guaranteed. With
> autoconf, users need not have the full developer tool chain installed.
> So, it's important that all the front-end generated files be up to
> date. Debian deals with these issues
Robert Jordens <[EMAIL PROTECTED]> writes:
> [Tue, 23 Mar 2004] Jack O'Quin wrote:
> > I always run `make' before `make dist' or `make distcheck'. I do that
> > to ensure that all distributed files are up-to-date. This is what the
> > "Goat Book" (_GNU Autoconf, Automake, and Libtool_) recommend
Hello!
[Tue, 23 Mar 2004] Jack O'Quin wrote:
> > it works after building it in the cvs checkout dir and then doing make
> > dist.
>
> I always run `make' before `make dist' or `make distcheck'. I do that
> to ensure that all distributed files are up-to-date. This is what the
> "Goat Book" (_GNU
Robert Joerdens <[EMAIL PROTECTED]> writes:
> Make dist doesn't work from a fresh checkout/autogen.sh:
>
> * depcomp is missing in CVS in config/ AFAICS
> * files/links seem to be missing for the config includes. make dist
> fails from a fresh checkout
...
> it works after building it in the cv
4 matches
Mail list logo
