Hi, i cannot upgrade squid because my ./configure fails (cause : sasl) checking sasl/sasl.h usability... no checking sasl/sasl.h presence... no checking for sasl/sasl.h... no checking sasl.h usability... no checking sasl.h presence... no checking for sasl.h... no checking for sasl_errstring in -lsasl2... no checking for sasl_errstring in -lsasl... no configure: error: Neither SASL nor SASL2 found With squid 3.2.9 i haven't this problem cyrus-sasl is installed but i don't need SASL. Have you got an idea ? Thanks for advance -- Best regards, Loïc BLOT, UNIX systems, security and network expert http://www.unix-experience.fr Le dimanche 28 avril 2013 à 01:49 +1200, Amos Jeffries a écrit : > The Squid HTTP Proxy team is very pleased to announce the availability > of the Squid-3.2.10 release! > > > This release is a bug fix release resolving several crashes and build > issues found in the prior releases. > > > Please note that with 3.3 series being STABLE the 3.2 series is > now officially deprecated. There are no longer any guaranteed of > future 3.2 releases. > > > The major changes to be aware of in this release: > > * running "squid -k reconfigure" drops rock cache > > Squid would happly run and report information about rock caches > until reconfigure. After which it would cease reporting the rock > caches existence, but continue to use it. > > > * multiple build issues on GNU Hurd, OpenBSD, FreeBSD, NetBSD > > GNU Hurd would fail to build with MAP_NORESERVE errors. > BSD systems would fail to build with enter_suid/leave_suid errors. > BSD systems were also unable to build SASL or LDAP helpers. > > > * crashes in ssl_crtd and basic_ncsa_auth helpers > > ssl_crtd on ARM systems would crash on startup. > basic_ncsa_auth build against recent glibc would crash during first > authentication process validating credentials. > > > * HTTP/1.1 compliance with no-cache="params" , private="params" > > Since caching was enabled for traffic containing Cache-Control:no-cache > Squid has been incorrectly caching traffic where that control > was passed a list of headers. Squid is now reverted to the old > behaviour when passed no-cache or private with parameters. > > > > See the ChangeLog for the full list of changes in this and earlier > releases. > > Users of Squid-3.2 with error page language negotiation are urged > to upgrade to this release or Squid-3.3.3 as soon as possible. > > All users of Squid-3.2 are encouraged to upgrade to the 3.3 series > stable release as soon as possible. > > > Please remember to run "squid -k parse" when testing upgrade to a new > version of Squid. It will audit your configuration files and report > any identifiable issues the new release will have in your installation > before you "press go". We are still removing the infamous "Bungled > Config" halting points and adding checks, so if something is not > identified please report it. > > > > Please refer to the release notes at > http://www.squid-cache.org/Versions/v3/3.2/RELEASENOTES.html > when you are ready to make the switch to Squid-3.2 > > Upgrade tip: > "squid -k parse" is starting to display even more > useful hints about squid.conf changes. > > This new release can be downloaded from our HTTP or FTP servers > > http://www.squid-cache.org/Versions/v3/3.2/ > ftp://ftp.squid-cache.org/pub/squid/ > ftp://ftp.squid-cache.org/pub/archive/3.2/ > > or the mirrors. For a list of mirror sites see > > http://www.squid-cache.org/Download/http-mirrors.html > http://www.squid-cache.org/Download/mirrors.html > > If you encounter any issues with this release please > file a bug report. > http://bugs.squid-cache.org/ > > > Amos Jeffries
Attachment:
signature.asc
Description: This is a digitally signed message part
