Ok, I need more detail - it doesn't make a lot of sense to me.  I ran 
./bootstrap.sh where you said, and it told me this:

Trying autoconf (GNU Autoconf) 2.59
autoheader: WARNING: Using auxiliary files such as `acconfig.h', `config.h.bot'
autoheader: WARNING: and `config.h.top', to define templates for `config.h.in'
autoheader: WARNING: is deprecated and discouraged.
autoheader:
autoheader: WARNING: Using the third argument of `AC_DEFINE' and
autoheader: WARNING: `AC_DEFINE_UNQUOTED' allows to define a template without
autoheader: WARNING: `acconfig.h':
autoheader:
autoheader: WARNING:   AC_DEFINE([NEED_FUNC_MAIN], 1,
autoheader:             [Define if a function `main' is needed.])
autoheader:
autoheader: WARNING: More sophisticated templates can also be produced, see the
autoheader: WARNING: documentation.
configure.in:13: warning: do not use m4_patsubst: use patsubst or m4_bpatsubst
aclocal.m4:628: AM_CONFIG_HEADER is expanded from...
configure.in:13: the top level
configure.in:1555: warning: AC_CHECK_TYPE: assuming `u_short' is not a type
autoconf/types.m4:234: AC_CHECK_TYPE is expanded from...
configure.in:1555: the top level
configure.in:2552: warning: do not use m4_regexp: use regexp or m4_bregexp
aclocal.m4:641: _AM_DIRNAME is expanded from...
configure.in:2552: the top level
configure.in:13: warning: do not use m4_patsubst: use patsubst or m4_bpatsubst
aclocal.m4:628: AM_CONFIG_HEADER is expanded from...
configure.in:13: the top level
configure.in:1555: warning: AC_CHECK_TYPE: assuming `u_short' is not a type
autoconf/types.m4:234: AC_CHECK_TYPE is expanded from...
configure.in:1555: the top level
configure.in:2552: warning: do not use m4_regexp: use regexp or m4_bregexp
aclocal.m4:641: _AM_DIRNAME is expanded from...
configure.in:2552: the top level
configure.in:2365: error: do not use LIBOBJS directly, use AC_LIBOBJ (see 
section `AC_LIBOBJ vs LIBOBJS'
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
autoconf failed
Autotool bootstrapping failed. You will need to investigate and correct
before you can develop on this source tree

Obviously I need some newer files, but I don't know where to get them or where 
to put them once I got them.  PLEASE HELP :D


 
 


-----Original Message-----
From: Chris Robertson [mailto:[EMAIL PROTECTED] 
Sent: Thursday, February 23, 2006 11:22 AM
To: squid-users@squid-cache.org
Subject: RE: [squid-users] post epoll...

> -----Original Message-----
> From: Gregori Parker [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 23, 2006 10:03 AM
> To: squid-users@squid-cache.org
> Subject: RE: [squid-users] post epoll...
> 
> 
> Interesting...
> 
> Here's what I did (downloaded patch from here
> http://devel.squid-cache.org/cgi-bin/diff2/epoll-2_5.patch?s2_5):
> 
>       #> tar zxvf squid.tar.gz
>       #> mv squid-2.5STABLE12/ squid
>       #> patch -p0 < epoll-2_5.patch
>       #> cd squid

./bootstrap.sh <--- This will complain if you don't have the preferred version 
of autoconf and automake.

>       #> ulimit -HSn 8192
>       #> ./configure --prefix=/usr/local/squid --enable-async-io
> --enable-snmp --enable-htcp --enable-underscores --enable-epoll
>       #> make
>       (etc..)
> 
> Can you help me understand what I missed?  I've never worked 
> with CVS or
> bootsrap.sh, so please be specific :) 
> 
> 

To the best of my knowledge, every one of the patch files on 
devel.squid-cache.org have a bootstrap.sh that needs to be run after the patch 
is applied.

Chris

Reply via email to