Re: [squid-users] error compiling squid-3.1.0.2 on ubuntu 8.10

From: Amos Jeffries <squid3_at_treenet.co.nz>
Date: Thu, 27 Nov 2008 18:24:20 +1300 (NZDT)

> Hi All,
>
> tried to compile squid squid-3.1.0.2 on ubuntu 8.10
>
> with the following options
> ./configure \
> --prefix=/usr \
> --localstatedir=/var \
> --libexecdir=${prefix}/lib/squid \
> --srcdir=. \
> --datadir=${prefix}/share/squid \
> --sysconfdir=/etc/squid \
> --with-default-user=prox \
> --with-logdir=/var/log \
> --enable-arp-acl
>
> below are all the errors found in config.log file
>

Many of these config.log 'errors' are simply Squid ./configure script
probing your system to locate various files. Many are expected to be
logged.
the important bit is whether anything is displayed when it halts.

<snip>

>
> executed make and got this error
>
> de -I../lib/libTrie/include -I../lib -I../lib -Werror -Wall
> -Wpointer-arith -Wwrite-strings -Wcomments -DDEFAULT_SQUID_CONFIG_DIR=
> \"/etc/squid\" -DDEFAULT_SQUID_DATA_DIR=\"/share/squid\" -g -O2 -MT
> ICAP/AsyncJob.lo -MD -MP -MF "$depbase.Tpo" -c -o ICAP/AsyncJob.lo
> ICAP/AsyncJob.cc; \
> then mv -f "$depbase.Tpo" "$depbase.Plo"; else rm -f "$depbase.Tpo";
> exit 1; fi
> mkdir ICAP/.libs
> g++ -DHAVE_CONFIG_H -DDEFAULT_CONFIG_FILE=\"/etc/squid/squid.conf\" -I.
> -I. -I../include -I. -I. -I../include -I../include
> -I../lib/libTrie/include -I../lib -I../lib -Werror -Wall -Wpointer-arith
> -Wwrite-strings -Wcomments -DDEFAULT_SQUID_CONFIG_DIR=\"/etc/squid\"
> -DDEFAULT_SQUID_DATA_DIR=\"/share/squid\" -g -O2 -MT ICAP/AsyncJob.lo
> -MD -MP -MF ICAP/.deps/AsyncJob.Tpo -c ICAP/AsyncJob.cc -fPIC -DPIC -o
> ICAP/.libs/AsyncJob.o
> cc1plus: warnings being treated as errors
> ICAP/AsyncJob.cc: In member function ‚€˜virtual const char*
> AsyncJob::status() const‚€™:
> ICAP/AsyncJob.cc:158: error: format not a string literal and no format
> arguments
> make[1]: *** [ICAP/AsyncJob.lo] Error 1
> make[1]: Leaving directory `/home/remy/rnd/squid-3.1.0.2/src'
> make: *** [all-recursive] Error 1
>
> can someone tell me what other packages are required to fix the above
> errors

I'm a bit braindead from a conference right now, but IIRC this was found
and fixed a while back.

Can you check whether the latest daily snapshot still has this or any
other problems please?

Cheers
Amos
Received on Thu Nov 27 2008 - 05:24:24 MST

This archive was generated by hypermail 2.2.0 : Thu Nov 27 2008 - 12:00:03 MST