Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: compile squid3.1.19 from source, error: Neither SASL nor SASL2 found

  1. #1
    Join Date
    Nov 2005
    Location
    Connecticut
    Beans
    82
    Distro
    Ubuntu 12.04 Precise Pangolin

    compile squid3.1.19 from source, error: Neither SASL nor SASL2 found

    Hey all,

    I am trying to comiple squid3 from source to get SSL enabled.

    Code:
    sudo apt-get build-essentials fakeroot devscripts openssl
    sudo apt-get build-dep squid3
    sudo apt-get source squid3
    When I do a
    Code:
    debuild -us -uc -b
    I get
    Code:
    error: Neither SASL nor SASL2 found
    I verified I have SASL2 installed, I even did a
    Code:
    sudo apt-get install libsasl2-2
    Heres the last lines of the buiid error
    Code:
    configure: Linux (Netfilter) Transparent Proxy enabled
    configure: Using POSIX_V6_LP64_OFF64 build environment
    configure: Auth scheme modules built: basic digest ntlm negotiate
    configure: Basic auth helpers built: LDAP MSNT NCSA PAM SASL SMB YP DB POP3 getpwnam squid_radius_auth multi-domain-NTLM
    configure: NTLM auth helpers built: smb_lm 
    configure: Negotiate auth helpers built: squid_kerb_auth
    configure: Digest auth helpers built: ldap password
    configure: External acl helpers built: ip_user ldap_group session unix_group wbinfo_group
    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
    make: *** [debian/stamp-autotools] Error 1
    dpkg-buildpackage: error: debian/rules build gave error exit status 2
    debuild: fatal error at line 1350:
    dpkg-buildpackage -rfakeroot -D -us -uc -b failed

  2. #2
    Join Date
    Jun 2007
    Beans
    16,470

    Re: compile squid3.1.19 from source, error: Neither SASL nor SASL2 found

    You shouldn't get that error if libsasl2-dev (2.1.25.dfsg1-6) is installed which build-dep should of pulled in.
    (your first posted command has 2 mistakes & wouldn't install anything, likely you mistyped in your post?

    More of an issue would be a cppunit error (fails to find at /usr), though that could be fixed
    I know nothing of this source ect. but would suspect that simply rebuilding using same rules wouldn't add the SSL support if not already enabled.
    (openssl seems to be a configure option

  3. #3
    Join Date
    Feb 2008
    Location
    Oblivion
    Beans
    Hidden!
    Distro
    Xubuntu

    Re: compile squid3.1.19 from source, error: Neither SASL nor SASL2 found

    Thread moved to General Help.

    Unsure why you posted in Ubuntu +1. That is now for Saucy (13.10) and your question doesn't relate to Ubuntu +1. Good luck.

  4. #4
    Join Date
    Nov 2005
    Location
    Connecticut
    Beans
    82
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: compile squid3.1.19 from source, error: Neither SASL nor SASL2 found

    Quote Originally Posted by mc4man View Post
    You shouldn't get that error if libsasl2-dev (2.1.25.dfsg1-6) is installed which build-dep should of pulled in.
    (your first posted command has 2 mistakes & wouldn't install anything, likely you mistyped in your post?

    More of an issue would be a cppunit error (fails to find at /usr), though that could be fixed
    I know nothing of this source ect. but would suspect that simply rebuilding using same rules wouldn't add the SSL support if not already enabled.
    (openssl seems to be a configure option
    Sorry that's a typo it should be the sudo apt-get install.

    Yes the configure option is:
    Code:
    ./configure --enable-ssl --enable-ssl-crtd

  5. #5
    Join Date
    Nov 2005
    Location
    Connecticut
    Beans
    82
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: compile squid3.1.19 from source, error: Neither SASL nor SASL2 found

    I moved it to the correct section, please delete this quesiton.

  6. #6
    Join Date
    Feb 2008
    Location
    Oblivion
    Beans
    Hidden!
    Distro
    Xubuntu

    Re: compile squid3.1.19 from source, error: Neither SASL nor SASL2 found

    Quote Originally Posted by jimmah6786 View Post
    I moved it to the correct section, please delete this quesiton.
    ? It is in the correct section. What is the link to the duplicate post? Not quite understanding ...

  7. #7
    Join Date
    Mar 2006
    Location
    Williams Lake
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: compile squid3.1.19 from source, error: Neither SASL nor SASL2 found

    It looks like the op created a new thread in Installation & Upgrades. I've closed that one, and any replies should continue in this thread.

  8. #8
    Join Date
    Feb 2008
    Location
    Oblivion
    Beans
    Hidden!
    Distro
    Xubuntu

    Re: compile squid3.1.19 from source, error: Neither SASL nor SASL2 found

    Quote Originally Posted by cariboo907 View Post
    It looks like the op created a new thread in Installation & Upgrades. I've closed that one, and any replies should continue in this thread.
    Ta.

  9. #9
    Join Date
    Apr 2008
    Location
    LOCATION=/dev/random
    Beans
    5,767
    Distro
    Ubuntu Development Release

    Re: compile squid3.1.19 from source, error: Neither SASL nor SASL2 found

    I think you need the sasl development files as well, not just the library...
    Code:
    sudo apt-get install libsasl2-dev
    Cheesemill

  10. #10
    Join Date
    Nov 2008
    Location
    Metro Boston
    Beans
    12,966
    Distro
    Kubuntu 14.04 Trusty Tahr

    Re: compile squid3.1.19 from source, error: Neither SASL nor SASL2 found

    If you want to push SSL through the proxy, I assume you are aware of SSLBump. I've tested it with 3.2.0.19, but it will not support transparent proxying until 3.3. You must tell the client to use the proxy for SSL and, of course, install the required server certificate so the proxy doesn't generate "man-in-the-middle" errors in the browser.

    If you want to use "dynamic SSL certificate generation" you should be compiling 3.2.
    Last edited by SeijiSensei; May 9th, 2013 at 03:54 AM.
    If you ask for help, do not abandon your request. Please have the courtesy to check for responses and thank the people who helped you.

    Blog · Linode System Administration Guides · Android Apps for Ubuntu Users

Page 1 of 2 12 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •