FYI, I was able to get past all of my issues by installing cyrus-sasl-devel. Apparently the fallback implementation that is there when cyrus is not available doesn't handle pipelining, and this was responsible for both the test failures and the interop issue. Andrew is working on fixing this.
--Rafael On Wed, Apr 22, 2015 at 3:02 PM, Gordon Sim <[email protected]> wrote: > On 04/22/2015 05:42 PM, Gordon Sim wrote: > >> On 04/21/2015 12:52 PM, Rafael Schloming wrote: >> >>> I'm seeing a couple of issues with the recently landed sasl changes. I'm >>> getting four test failures in the python tests (see details at the end). >>> I'm also seeing interop issues with the proton.js built prior to these >>> changes, and with these changes in place the javascript build seems to be >>> messed up (not finding new symbols). >>> >>> Is anyone else seeing similar issues? >>> >> >> I can't even get as far as the tests. On a clean build >> (cyrus-sasl-lib-2.1.23-31 installed) I get: >> >> /home/gordon/projects/proton-git/proton-c/src/sasl/cyrus_sasl.c: In >>> function ‘pn_sasl_free’: >>> /home/gordon/projects/proton-git/proton-c/src/sasl/cyrus_sasl.c:656:15: >>> error: >>> implicit declaration of function ‘sasl_client_done’ >>> [-Wimplicit-function-declaration] >>> /home/gordon/projects/proton-git/proton-c/src/sasl/cyrus_sasl.c:658:15: >>> error: >>> implicit declaration of function ‘sasl_server_done’ >>> [-Wimplicit-function-declaration] >>> make[2]: *** >>> [proton-c/CMakeFiles/qpid-proton.dir/src/sasl/cyrus_sasl.c.o] Error 1 >>> >> > This is a cyrus version issue, see > https://issues.apache.org/jira/browse/PROTON-859 > > If I set the SASL_IMPL in cmake to null (is that how you turn it off), >> then I get: >> > > I got past this with a completely fresh build directory. > > >
