One more thing, is there a way to deactivate everything related to
authentication and SSL? Because for now, we want to test the Qpid C++
broker basic features without any authentication but just using anonymous.

On Wed, Mar 23, 2016 at 5:43 PM, Adel Boutros <[email protected]> wrote:

> I just installed Cyrus cyrus-sasl-2.1.23-13.el6_3.1.x86_64 (yum install
> cyrus-imapd) and executed ctest command again but still same error. Should
> I re-launch cmake?
>
> For information:
>
> bash$ cat /proc/version
> Linux version 2.6.32-358.el6.x86_64 (
> [email protected]) (gcc version 4.4.7 20120313
> (Red Hat 4.4.7-3) (GCC) ) #1 SMP Tue Jan 29 11:47:41 EST 2013
>
>
> On Wed, Mar 23, 2016 at 5:27 PM, Gordon Sim <[email protected]> wrote:
>
>> On 23/03/16 15:59, Adel Boutros wrote:
>>
>>> Hello,
>>>
>>> I am trying to compile Qpid 0.34 on Linux with the below configuration.
>>> The
>>> compilatio is successful. Nevertheless I have some tests failing. Can you
>>> please give me some hints on what I might have done wrong?
>>>
>>> *Config*
>>>
>>>     - Qpid: 0.34
>>>     - Proton: 0.12
>>>     - Boost: 1.55.0
>>>     - Cmake/Ctest: 3.2.3
>>>
>>> *Commands (Assuming Boost and Proton are already built)*
>>> cmake -G "Unix Makefiles" $QPID_SOURCE_DIR
>>> -DCMAKE_INSTALL_PREFIX=$EXP_QPID_TARGET_DIR
>>> -DCMAKE_CXX_FLAGS=-Wno-error=switch -DBOOST_ROOT=$EXP_BOOST_TARGET_DIR
>>> -DProton_DIR="$PROTON_TARGET_DIR"
>>>
>>> make install
>>>
>>> ctest -R unit_test -V
>>>
>>> *Errors*
>>>
>>> 3: Running 333 test cases...
>>> 3: ***************************unknown location(0): fatal error in
>>> "testAuthenticatedUsername": std::exception: Can't authenticate using
>>> PLAIN
>>> 3:
>>>
>>> /data/jenkins-slave/home/workspace/adel/qpid/cpp/src/tests/MessagingSessionTests.cpp(861):
>>> last checkpoint
>>>
>>
>> Do you have the cyrus-sasl libs/headers installed (cyrus-sasl-devel on
>> fedora)?
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>

Reply via email to