Hallo, Amos, Du meintest am 08.03.13: >>> The Squid HTTP Proxy team is very pleased to announce the >>> availability of the Squid-3.3.2 release! >> Compiling it on one of my machines stopped with >> >> depbase=`echo peer_proxy_negotiate_auth.o | sed 's|[^/]*$|.deps/ >> &|;s|\.o$||'`;\ >> g++ -DHAVE_CONFIG_H -DDEFAULT_CONFIG_FILE=\"/etc/squid/squid.conf\" >> -DDEFAULT_SQUID_DATA_DIR=\"/usr/share/squid\" >> -DDEFAULT_SQUID_CONFIG_DIR=\"/etc/squid\" -I.. -I../include >> -I../lib -I../src -I../include -I/usr/heimdal/include [...] >> deprecated (declared at /usr/heimdal/include/krb5-protos.h:2284) >> [-Werror=deprecated-declarations] cc1plus: all warnings being >> treated as errors make[3]: *** [peer_proxy_negotiate_auth.o] Error 1 >> make[3]: Leaving directory `/tmp/SBo/squid-3.3.2/src' >> May be related in some strange way with the kerberos installation; >> on another machine compiling worked, but when running it stopped >> with a kerberos related error message. >> >> (My kerberos installations may be corrupt, but that should be >> another problem) > It would be best to sort that out krb5 stuff first IMO. The above > warnings are about internal errors in the krb5 installation. Next try: compiling on a machine without any kerberos installation (neither MIT nor Heimdal). stopped with libtool: link: cannot find the library `/usr/lib/libcom_err.la' or unhandled argument `/usr/lib/libcom_err.la' That file is at least part of the heimdal packet. > Once you have krb5 sorted out if it is still halting Squid build you > can use --disable-strict-error-checking to get Squid to build. The > usual lack of guarantees about both operation and future build > success if you use it regularly though. Isn't there any switch "--without kerberos" or so? Viele Gruesse! Helmut
