Robbie,
Thanks for reply.
My apologies I missed the commit fixing the issue.

Alex

On 16 September 2016 at 11:27, Robbie Gemmell <[email protected]> wrote:
> As I've mentioned on the JIRA, it looks like this commit yesterday was
> about addressing that:
> https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;a=commit;h=44875208
>
> Robbie
>
> On 16 September 2016 at 10:28, Oleksandr Rudyy <[email protected]> wrote:
>> Hi all,
>> The proton-c build failed as part of jenkins job Qpid-Python-Java-Test
>> [1] with the following error
>>
>> Linking CXX shared library libqpid-proton-cpp.so
>> CMakeFiles/qpid-proton-cpp.dir/src/connector.cpp.o: In function
>> `proton::connector::on_transport_closed(proton::proton_event&)':
>> /home/jenkins/jenkins-slave/workspace/Qpid-Python-Java-Test/qpid-proton/proton-c/bindings/cpp/src/connector.cpp:83:
>> undefined reference to `proton::timestamp::now()'
>> collect2: ld returned 1 exit status
>> make[2]: *** [proton-c/bindings/cpp/libqpid-proton-cpp.so.9.0.0] Error 1
>> make[1]: *** [proton-c/bindings/cpp/CMakeFiles/qpid-proton-cpp.dir/all] 
>> Error 2
>> make: *** [all] Error 2
>>
>>
>> It looks like chrono library was not available on jenkins node and
>> now() was not defined but it was still referenced...
>>
>> The job prints names of installed packages and available libraries
>> into its log [2].
>>
>> Kind Regards,
>> Alex
>>
>> [1] 
>> https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Python-Java-Test/1154/
>> [2] 
>> https://builds.apache.org/view/M-R/view/Qpid/job/Qpid-Python-Java-Test/1154/console
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to