See <http://build.squid-cache.org/job/3.HEAD-i386-OpenBSD-4.5/472/changes>
Changes:
[Amos Jeffries <amosjeffries_at_squid-cache.org>] Fix omitted part of rev10654
[Alex Rousskov <rousskov_at_measurement-factory.com>] Fixed comm.cc:377: "fd_table[fd].halfClosedReader != NULL" assertion
Client side must stop reading when switching to a tunnel mode. The old code
called low-level commSetSelect to stop reading, but that left Comm tables in
an inconsistent state, with the client side reader callback still scheduled.
Squid would assert when the tunnel called comm_read with its own callback.
The bug is unrelated to half-closed connections despite halfClosedReader
mentioned in the assertion text. The assertion means "no more than one active
reader per FD".
------------------------------------------
Started by upstream project "3.HEAD-amd64-CentOS-5.3" build number 673
Building remotely on vobsd
M src/cf_gen.cc
All changes applied successfully.
Now on revision 10659.
+ ./test-builds.sh --verbose --use-config-cache
+ CC=ccache gcc CXX=ccache g++
TESTING: layer-00-bootstrap
total 16
drwxr-xr-x 2 hudson hudson 4096 Jul 23 08:54 .
drwxr-xr-x 26 hudson hudson 4096 Jul 23 08:54 ..
sysctl: second level name smp in kern.smp.cpus is invalid
.././test-suite/buildtest.sh[30]: [: -gt: unexpected operator/operand
BUILD: .././test-suite/buildtests/layer-00-bootstrap.opts
automake (1.9) : automake
autoconf (2.62) : autoconf
libtool (1.5) : libtool
libtool path : /usr/local/bin
Bootstrapping
compat/Makefile.am:12: Libtool library used but `LIBTOOL' is undefined
compat/Makefile.am:12:
compat/Makefile.am:12: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
compat/Makefile.am:12: to `configure.in' and run `aclocal' and `autoconf' again.
src/Makefile.am:153: Libtool library used but `LIBTOOL' is undefined
src/Makefile.am:153:
src/Makefile.am:153: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/Makefile.am:153: to `configure.in' and run `aclocal' and `autoconf' again.
src/acl/Makefile.am:4: Libtool library used but `LIBTOOL' is undefined
src/acl/Makefile.am:4:
src/acl/Makefile.am:4: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/acl/Makefile.am:4: to `configure.in' and run `aclocal' and `autoconf' again.
src/adaptation/Makefile.am:15: Libtool library used but `LIBTOOL' is undefined
src/adaptation/Makefile.am:15:
src/adaptation/Makefile.am:15: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/adaptation/Makefile.am:15: to `configure.in' and run `aclocal' and `autoconf' again.
src/adaptation/ecap/Makefile.am:4: Libtool library used but `LIBTOOL' is undefined
src/adaptation/ecap/Makefile.am:4:
src/adaptation/ecap/Makefile.am:4: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/adaptation/ecap/Makefile.am:4: to `configure.in' and run `aclocal' and `autoconf' again.
src/adaptation/icap/Makefile.am:4: Libtool library used but `LIBTOOL' is undefined
src/adaptation/icap/Makefile.am:4:
src/adaptation/icap/Makefile.am:4: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/adaptation/icap/Makefile.am:4: to `configure.in' and run `aclocal' and `autoconf' again.
src/auth/Makefile.am:7: Libtool library used but `LIBTOOL' is undefined
src/auth/Makefile.am:7:
src/auth/Makefile.am:7: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/auth/Makefile.am:7: to `configure.in' and run `aclocal' and `autoconf' again.
src/base/Makefile.am:5: Libtool library used but `LIBTOOL' is undefined
src/base/Makefile.am:5:
src/base/Makefile.am:5: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/base/Makefile.am:5: to `configure.in' and run `aclocal' and `autoconf' again.
src/comm/Makefile.am:4: Libtool library used but `LIBTOOL' is undefined
src/comm/Makefile.am:4:
src/comm/Makefile.am:4: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/comm/Makefile.am:4: to `configure.in' and run `aclocal' and `autoconf' again.
src/esi/Makefile.am:4: Libtool library used but `LIBTOOL' is undefined
src/esi/Makefile.am:4:
src/esi/Makefile.am:4: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/esi/Makefile.am:4: to `configure.in' and run `aclocal' and `autoconf' again.
src/eui/Makefile.am:4: Libtool library used but `LIBTOOL' is undefined
src/eui/Makefile.am:4:
src/eui/Makefile.am:4: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/eui/Makefile.am:4: to `configure.in' and run `aclocal' and `autoconf' again.
src/fs/Makefile.am:3: Libtool library used but `LIBTOOL' is undefined
src/fs/Makefile.am:3:
src/fs/Makefile.am:3: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/fs/Makefile.am:3: to `configure.in' and run `aclocal' and `autoconf' again.
src/icmp/Makefile.am:25: Libtool library used but `LIBTOOL' is undefined
src/icmp/Makefile.am:25:
src/icmp/Makefile.am:25: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/icmp/Makefile.am:25: to `configure.in' and run `aclocal' and `autoconf' again.
src/ident/Makefile.am:4: Libtool library used but `LIBTOOL' is undefined
src/ident/Makefile.am:4:
src/ident/Makefile.am:4: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/ident/Makefile.am:4: to `configure.in' and run `aclocal' and `autoconf' again.
src/ip/Makefile.am:4: Libtool library used but `LIBTOOL' is undefined
src/ip/Makefile.am:4:
src/ip/Makefile.am:4: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/ip/Makefile.am:4: to `configure.in' and run `aclocal' and `autoconf' again.
src/ipc/Makefile.am:4: Libtool library used but `LIBTOOL' is undefined
src/ipc/Makefile.am:4:
src/ipc/Makefile.am:4: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/ipc/Makefile.am:4: to `configure.in' and run `aclocal' and `autoconf' again.
src/log/Makefile.am:4: Libtool library used but `LIBTOOL' is undefined
src/log/Makefile.am:4:
src/log/Makefile.am:4: The usual way to define `LIBTOOL' is to add `AC_PROG_LIBTOOL'
src/log/Makefile.am:4: to `configure.in' and run `aclocal' and `autoconf' again.
automake failed
Autotool bootstrapping failed. You will need to investigate and correct
before you can develop on this source tree
buildtest.sh result is 1
BUILD: .././test-suite/buildtests/layer-00-bootstrap.opts
Build FAILED.
Received on Fri Jul 23 2010 - 06:55:53 MDT
This archive was generated by hypermail 2.2.0 : Fri Jul 23 2010 - 12:00:10 MDT