| Summary: | errors in Squid-2.3.4's configure prevent ipf configuration | ||
|---|---|---|---|
| Product: | Ports & Packages | Reporter: | root <root> |
| Component: | Individual Port(s) | Assignee: | Adrian Chadd <adrian> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | CC: | squid-bugs |
| Priority: | Normal | ||
| Version: | Latest | ||
| Hardware: | Any | ||
| OS: | Any | ||
Responsible Changed From-To: freebsd-ports->peter Over to maintainer Responsible Changed From-To: peter->adrian New maintainer Has this been fixed? On 22 Sep, David W. Chapman Jr. wrote:
> Has this been fixed?
I don't know... By who? By squid or by us?
-mi
State Changed From-To: open->closed This has been fixed in the latest squid (version 2.4). Thanks for your report! |
The lines in the squid's configure, that check for ip-filter are erroneous -- the test(1) invocations have ``=='' instead of ``=''. If I uncomment the (off-by-default): CONFIGURE_ARGS+= --enable-ipf-transparent in the port's Makefile, the configure will fail with test(1) complaining about syntax errors. Fix: Squid should, of course, fix this ASAP. But until that happens, dropping the following into /usr/ports/www/squid23/patches/patch-pl will ensure the port builds on *BSD: +++ configure Tue Sep 12 16:50:22 2000 @@ -4452,10 +4452,10 @@ echo "configure:4460: checking if IP-Filter header files are installed" >&5 # hold on to your hats... if test "$ac_cv_header_ip_compat_h" = "yes" || test "$ac_cv_header_ip_fil_compat_h" = "yes" || - test "$ac_cv_header_netinet_ip_compat_h" == "yes" || - test "$ac_cv_header_netinet_ip_fil_compat_h" == "yes" ; then + test "$ac_cv_header_netinet_ip_compat_h" = "yes" || + test "$ac_cv_header_netinet_ip_fil_compat_h" = "yes" ; then have_ipfilter_compat_header="yes" fi if test "x$have_ipfilter_compat_header" = "xyes" && test "$ac_cv_header_ip_fil_h" = "yes" && --VAA91348.968807428/monsta.privatelabs.com-- How-To-Repeat: See description.