Try updating your CPPFLAGS with -I and the full path to those headers perhaps? Once I had both installed this worked for me, but I was not using nonstandard paths.
On Sunday, August 16, 2015, F21 <[email protected]> wrote: > Hey Jeff, > > I do have all headers and libraries installed in > /home/user/Desktop/libsasl2 as they are compiled manually (I plan to pack > the required files together with mesos into a package later on). > > I can see that ./configure does find the headers for libsasl2, but it > can't see the plugins (which includes CRAM-MD5) inside > /home/user/Desktop/libsasl2/lib/sasl2. > > Sasl2 does warn that as I am installing to /home/user/Desktop/libsasl2, I > would need to set SASL_PATH to /home/user/Desktop/libsasl2/lib/sasl2, but > setting that environment variable didn't help. > > Is there anyway to let ./configure see the plugins in > /home/user/Desktop/libsasl2/lib/sasl2? > > On 17/08/2015 2:45 PM, Jeff Schroeder wrote: > > Yes, the same thing happened to me at first. You need both the headers > (the dev package and .h files) and the actual libraries installed. > > On Sunday, August 16, 2015, F21 <[email protected] > <javascript:_e(%7B%7D,'cvml','[email protected]');>> wrote: > >> I am trying to build mesos 0.23. >> >> In my case, I am trying to build mesos and all of its dependencies >> manually, so I can build a package that contains everything. >> >> I am building cyrus sasl 2.1.26 like so: >> >> ./configure CC=gcc-4.8 CPPFLAGS=-I/usr/include/openssl >> --prefix=/home/user/Desktop/libsasl2 --enable-cram >> make >> make install >> >> Mesos is being build like so (modified from the instructions in the docs): >> ../configure CC=gcc-4.8 CXX=g++-4.8 >> LD_FLAGS=-L/home/user/Desktop/libsasl2/lib >> SASL_PATH=/home/user/Desktop/libsasl2/lib/sasl2 >> --prefix=/home/user/Desktop/mesos-install --with-svn=/home/user/Desktop/svn >> --with-apr=/home/user/Desktop/apr --with-sasl=/home/user/Desktop/libsasl2 >> >> For some reason, mesos will error because CRAM-MD5 is not found during >> ./configure: >> >> checking for sasl_done in -lsasl2... yes >> checking SASL CRAM-MD5 support... configure: error: no >> ------------------------------------------------------------------- >> We need CRAM-MD5 support for SASL authentication. >> ------------------------------------------------------------------- >> >> However, I do have CRAM-MD5 support for my compiled libsasl2. In >> /home/user/Desktop/libsasl2/lib/sasl2, I see libcrammd5.so, >> libcrammd5.so.3, libcrammd5.so.3.0.0, libcrammd5.a and libcrammd5.la >> >> If I run the pluginviewer executable that is created when building >> libsasl2, it shows that the CRAM-MD5 plugin is loaded. >> >> Any ideas what might be happening here? >> > > > -- > Text by Jeff, typos by iPhone > > > -- Text by Jeff, typos by iPhone
