----- Original Message -----
From: "Henrik Nordstrom" <hno@squid-cache.org>
To: "Robert Collins" <robert.collins@itdomain.com.au>
Cc: "Klavs Klavsen" <ktk@metropol.dk>; <squid-dev@squid-cache.org>
> > For the record:
> > bootstrap.sh should ONLY be run when
> > * you have autoconf 2.13 and automake 1.5 (or 1.6) installed.
> > * You have altered (by hand or via patch) configure.in, or any
> > Makefile.am.
>
> Which means he should run bootstrap.sh, as the rproxy patch modifies
> both configure.in and src/Makefile.am.
Cool. (I wasn't sure if it did or didn't).
> > If you are doing multiple compilations from the same source then you
> > should use --enable-dependency-tracking on your configure line to
ensure
> > that source changes will recompile related files.
>
> The dependency checks are enabled by default. Actually, the
> --enable-dependency-tracking option seems to be a no-op. Cannot find
> anything it changes from the default. Don't know why automake insists
on
> listing both --enable-dependency-tracking and
> --disable-dependency-tracking in the configure help...
IIRC when we run automake we can specify the default to be used. Also,
one can edit configure.in to force it but if that's done, the user
should still have the right to over-rule. I agree that listing both is
unusual, as the reverse is implied.
Rob
Received on Sat Oct 20 2001 - 08:54:36 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:14:34 MST