Menu

Compiling on FreeBSD

Help
Ed Heil
2001-05-04
2002-01-02
  • Ed Heil

    Ed Heil - 2001-05-04

    I'm having a bitch of a time trying to compile this on FreeBSD.

    It always complains about lack of sasl.  Now, I have sasl installed from the BSD ports collection...  it's in /usr/local/lib/sasl and /usr/local/include/sasl.

    But no matter what I do I seem to get a "cannot continue without libsasl" error.

    I even hacked the configure script to change "ac_cv_sasl_where_lib=${with_sasl}/lib" to "ac_cv_sasl_where_lib=${with_sasl}/lib/sasl" -- and the same thing with the headers dir -- and then ran ./configure --with-sasl=/usr/local

    but I still ended up with:

    ./configure: LIB_SASL-L/usr/local/lib/sasl: not found  
    checking for sasl.h... yes                             
    checking for sasl_getprop in -lsasl... no              
    configure: error: Cannot continue without libsasl.     
    Get it from ftp://ftp.andrew.cmu.edu:/pub/cyrus-mail/. 

    any ideas where I'm going wrong?

     
    • Tim Martin

      Tim Martin - 2001-07-13

      Sorry for the delay in replying.

      Yeah, I don't like how freebsd trys to put libsasl in /usr/local/include/sasl instead of /usr/local/include. It's possible the configure script can't deal with this correctly. I'd try making links in /usr/local/include and /usr/local/lib to the appropriate files.

       
      • Sean Goller

        Sean Goller - 2002-01-02

        Actually, the problem is because of a typo in the configure script, on top of the "freebsd likes to stick include files in stupid places" issue.

        line 1420 in configure is as follows:

                  LIB_SASL"-L$ac_cv_sasl_where_lib"

        there should be an '=' between LIB_SASL and the rest of the line.

        As for the general freebsd include file problem, I modified the configure script just a couple lines above, setting ac_cv_sasl_where_inc to be ${with_sasl}/include/sasl which takes care of the problem. I also used gmake to build instead of the freebsd make.

        Oh yeah, Hi Tim. :)

        -Sean.

         

Log in to post a comment.

MongoDB Logo MongoDB