Solved Error updating squid from ports 4.10->4.11

U

user_bsd

Hi
When updating a squid from ports, an error occurs.
Has anyone had such an error?
How can this error be eliminated or need to wait for squid updates?

(11.3-RELEASE-p7)


Code: 
--- support_krb5.o ---
depbase=`echo support_krb5.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`; c++ -DHAVE_CONFIG_H -DDEFAULT_CONFIG_FILE=\"/usr/local/etc/squid/squid.conf\"  -DDEFAULT_SQUID_DATA_DIR=\"/usr/local/etc/squid\"  -DDEFAULT_SQUID_CONFIG_DIR=\"/usr/local/etc/squid\"    -I../../../.. -I../../../../include  -I../../../../lib -I../../../../src  -I../../../../include  -I/usr/local/include/heimdal  -I../../../../libltdl -I. -I/usr/include -I/usr/local/include -I/usr/local/include -D_REENTRANT -I/usr/include -I/usr/include -O2 -pipe -I/usr/local/include -I/usr/local/include -fstack-protector-strong -DLDAP_DEPRECATED -fno-strict-aliasing   -I/usr/local/include -MT support_krb5.o -MD -MP -MF $depbase.Tpo -c -o support_krb5.o support_krb5.cc && mv -f $depbase.Tpo $depbase.Po
support_krb5.cc:470:24: error: no member named 'keyblock' in 'krb5_creds'
                creds->keyblock.enctype = 0;
                ~~~~~  ^
support_krb5.cc:471:28: error: no member named 'keyblock' in 'krb5_creds'
                if (creds->keyblock.contents)
                    ~~~~~  ^
support_krb5.cc:472:73: error: no member named 'keyblock' in 'krb5_creds'
                    krb5_free_keyblock_contents(kparam.context, &creds->keyblock);
                                                                 ~~~~~  ^
3 errors generated.
*** [support_krb5.o] Error code 1

make[6]: stopped in /usr/ports/www/squid/work/squid-4.11/src/acl/external/kerberos_ldap_group
1 error

make[6]: stopped in /usr/ports/www/squid/work/squid-4.11/src/acl/external/kerberos_ldap_group
*** [all-recursive] Error code 1

make[5]: stopped in /usr/ports/www/squid/work/squid-4.11/src/acl/external
1 error

make[5]: stopped in /usr/ports/www/squid/work/squid-4.11/src/acl/external
*** [all-recursive] Error code 1

make[4]: stopped in /usr/ports/www/squid/work/squid-4.11/src/acl
1 error

make[4]: stopped in /usr/ports/www/squid/work/squid-4.11/src/acl
*** [all-recursive] Error code 1

make[3]: stopped in /usr/ports/www/squid/work/squid-4.11/src
1 error

make[3]: stopped in /usr/ports/www/squid/work/squid-4.11/src
*** [all] Error code 2

make[2]: stopped in /usr/ports/www/squid/work/squid-4.11/src
1 error

make[2]: stopped in /usr/ports/www/squid/work/squid-4.11/src
*** [all-recursive] Error code 1

make[1]: stopped in /usr/ports/www/squid/work/squid-4.11
1 error

make[1]: stopped in /usr/ports/www/squid/work/squid-4.11
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1

Stop.
make: stopped in /usr/ports/www/squid
** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20200423-88979-ch4hle env UPGRADE_TOOL=portupgrade UPGRADE_PORT=squid-4.10 UPGRADE_PORT_VER=4.10 make BATCH=yes
** Fix the problem and try again.
 
Do you need Kerberos support for Squid? If not, you could try turning that off:
Code: 
     GSSAPI_NONE=off: Disable GSSAPI support
     GSSAPI_BASE=on: GSSAPI support via base system (needs Kerberos)
     GSSAPI_HEIMDAL=off: GSSAPI support via security/heimdal
     GSSAPI_MIT=off: GSSAPI support via security/krb5

The error indicates a problem with Kerberos, not sure why though.
 
Do you need Kerberos support for Squid?
Click to expand...
I am using Squid + Kerberos-authentication through Active Directory
 

Attachments

  • conf_squid_gss.png
    conf_squid_gss.png
    4.5 KB · Views: 106
I conducted several tests and found out that the error occurs when you turn on AUTH_SASL.

Code: 
--> [x] AUTH_SASL       Install SASL authentication helpers  <---
 
That option is off by default, so the issue probably didn't surface during the test builds. You may want to report it so it can be fixed.
 
You must log in or register to reply here.
Back
Top