Alex Rousskov wrote:
On 07/09/2009 01:40 AM, Amos Jeffries wrote:
Amos Jeffries wrote:
Well, I've found a possible reason to disable them by default.
The Debian Lenny/Ubuntu Jaunty libtool 2.2 appears broken with its
handling of the libtool convenience library. Giving build failures
unless they are configured to off.
Since I made the change to testbed "distcheck" I've been fighting with
them. Something inside distcheck seems to be running configure with
the defaults regardless of what the master test is run with. Probably
the dist "configure --silent" packaging or a sub-test of the package
it makes.
If anyone is able to help I'd be very grateful. If we can't find a
solution to that one I think we are going to have to disable loadable
modules unless adaptation needs them.
Amos
Confirmed:
c_install_base=`CDPATH="${ZSH_VERSION+.}:" && cd squid-3.HEAD-BZR/_inst
&& pwd | sed -e 's,^[^:\\/]:[\\/],/,'` \
&& dc_destdir="${TMPDIR-/tmp}/am-dc-$$/" \
&& cd squid-3.HEAD-BZR/_build \
&& ../configure --srcdir=.. --prefix="$dc_install_base" \
\
&& make \
&& make dvi \
&& make check \
&& make install \
&& make installcheck \
&& make uninstall \
...
&& make dist \
&& rm -rf squid-3.HEAD-BZR.tar.gz squid-3.HEAD-BZR.tar.bz2 \
&& make distcleancheck
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
...
checking whether to use loadable modules... yes, implicitly
Will setting DISTCHECK_CONFIGURE_FLAGS in top Makefile.am help with this?
Alex.
That worked for the distcheck breakage.
Now only to fix the libtool bug that brought it to attention.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE6 or 3.0.STABLE16
Current Beta Squid 3.1.0.9
