Re: qpid-cpp cmake fails to find proton when PKG_CONFIG_PATH is set to non-standard /lib[64]/pkgconfig

[Justin Ross]

Seems likely that it's this change of mine.

https://github.com/apache/qpid-cpp/commit/b18583a6c05d0bb8cb9502f0823d902e17b2410e

I'll try to reproduce and see if this really the cause.

On Mon, Mar 19, 2018 at 12:28 PM, Robbie Gemmell 
wrote:

> I see the same thing on Fedora 26 too. There have been cmake-related
> changes on qpid-cpp and qpid-proton masters in recent days, its not
> immediately clear to me whether it is one or the other, or both.
>
> On 19 March 2018 at 17:15, Oleksandr Rudyy  wrote:
> > Hi,
> >
> > Jenkins job Qpid-Broker-J-Python-Test started to fail due to an issue
> > with building cpp broker. The job was building qpid-cpp broker
> > successfully before 15th of March.
> >
> > The jobs installs proton into non-standard location and sets
> > PKG_CONFIG_PATH as specified in qpid-cpp INSTALL.txt.
> >
> > However, cmake fails to find proton and reports the following error:
> >
> > CMake Error: The following variables are used in this project, but
> > they are set to NOTFOUND.
> > Please set them or make sure they are set and tested correctly in the
> > CMake files:
> > Proton_LIBRARY
> > linked by target "amqp" in directory
> > /home/jenkins/jenkins-slave/workspace/Qpid-Broker-J-
> Python-Test/qpid-cpp/src
> > linked by target "qpidmessaging" in directory
> > /home/jenkins/jenkins-slave/workspace/Qpid-Broker-J-
> Python-Test/qpid-cpp/src
> >
> > What is interesting, that when both qpid broker and proton have the
> > same install prefix, proton is found successfully by cmake.
> >
> >
> > I can change the job to build qpid and proton with the same install
> > prefix, though, I would like to clarify whether the build scripts have
> > been changed intentionally  and setting of PKG_CONFIG_PATH as
> > described in INSTALL.txt is not supported any-more.
> >
> > I built on Fedora 27. Jenkins job is running on Ubuntu.
> > For both environments the same cmake error is reported with
> PKG_CONFIG_PATH.
> >
> > Kind Regards,
> > Alex
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> > For additional commands, e-mail: users-h...@qpid.apache.org
> >
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: qpid-cpp cmake fails to find proton when PKG_CONFIG_PATH is set to non-standard /lib[64]/pkgconfig

[Robbie Gemmell]

I see the same thing on Fedora 26 too. There have been cmake-related
changes on qpid-cpp and qpid-proton masters in recent days, its not
immediately clear to me whether it is one or the other, or both.

On 19 March 2018 at 17:15, Oleksandr Rudyy  wrote:
> Hi,
>
> Jenkins job Qpid-Broker-J-Python-Test started to fail due to an issue
> with building cpp broker. The job was building qpid-cpp broker
> successfully before 15th of March.
>
> The jobs installs proton into non-standard location and sets
> PKG_CONFIG_PATH as specified in qpid-cpp INSTALL.txt.
>
> However, cmake fails to find proton and reports the following error:
>
> CMake Error: The following variables are used in this project, but
> they are set to NOTFOUND.
> Please set them or make sure they are set and tested correctly in the
> CMake files:
> Proton_LIBRARY
> linked by target "amqp" in directory
> /home/jenkins/jenkins-slave/workspace/Qpid-Broker-J-Python-Test/qpid-cpp/src
> linked by target "qpidmessaging" in directory
> /home/jenkins/jenkins-slave/workspace/Qpid-Broker-J-Python-Test/qpid-cpp/src
>
> What is interesting, that when both qpid broker and proton have the
> same install prefix, proton is found successfully by cmake.
>
>
> I can change the job to build qpid and proton with the same install
> prefix, though, I would like to clarify whether the build scripts have
> been changed intentionally  and setting of PKG_CONFIG_PATH as
> described in INSTALL.txt is not supported any-more.
>
> I built on Fedora 27. Jenkins job is running on Ubuntu.
> For both environments the same cmake error is reported with PKG_CONFIG_PATH.
>
> Kind Regards,
> Alex
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

qpid-cpp cmake fails to find proton when PKG_CONFIG_PATH is set to non-standard /lib[64]/pkgconfig

[Oleksandr Rudyy]

Hi,

Jenkins job Qpid-Broker-J-Python-Test started to fail due to an issue
with building cpp broker. The job was building qpid-cpp broker
successfully before 15th of March.

The jobs installs proton into non-standard location and sets
PKG_CONFIG_PATH as specified in qpid-cpp INSTALL.txt.

However, cmake fails to find proton and reports the following error:

CMake Error: The following variables are used in this project, but
they are set to NOTFOUND.
Please set them or make sure they are set and tested correctly in the
CMake files:
Proton_LIBRARY
linked by target "amqp" in directory
/home/jenkins/jenkins-slave/workspace/Qpid-Broker-J-Python-Test/qpid-cpp/src
linked by target "qpidmessaging" in directory
/home/jenkins/jenkins-slave/workspace/Qpid-Broker-J-Python-Test/qpid-cpp/src

What is interesting, that when both qpid broker and proton have the
same install prefix, proton is found successfully by cmake.


I can change the job to build qpid and proton with the same install
prefix, though, I would like to clarify whether the build scripts have
been changed intentionally  and setting of PKG_CONFIG_PATH as
described in INSTALL.txt is not supported any-more.

I built on Fedora 27. Jenkins job is running on Ubuntu.
For both environments the same cmake error is reported with PKG_CONFIG_PATH.

Kind Regards,
Alex

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: qpid-proton cpp - Broker example segfault

[Alan Conway]

On Mon, Mar 19, 2018 at 12:07 PM, Baptiste Robert <
baptisterober...@gmail.com> wrote:

> Thank you for your answer, It fixed my issues. Maybe it's due tthe
> partial support of C++11 integrated in GCC 4.6.2.
>
In the same way, is it possible to build the last qpid-proton version with
> OpenSSL 1.0.0 ? Since the 0.19 version I cannot built it, is it possible to
> set a cmake variable to make it compliant ?
>
>
I'm glad you got the C++ issue sorted out. I don't know about the SSL
problem. It is probably possible to work around it but I'm not aware of a
fix already in the cmake files.Perhaps someone else on the list can answer
that.



> Thank you,
>
>
> 2018-03-19 15:21 GMT+01:00 Alan Conway :
>
> > On Mon, Mar 19, 2018 at 4:45 AM, Baptiste Robert <
> > baptisterober...@gmail.com
> > > wrote:
> >
> > > Hello,
> > >
> > > I'm having an issue with the broker example. When I run it works, but a
> > > soon as I send messages to it I get a segfault. I send messages with
> the
> > > examples simple_send.
> > >
> > > Note : I compiled the broker with gcc 4.6.2 e.g. without C++11 support,
> > and
> > > I'm supposing that is the root cause of a lot of my problem with qpid..
> > >
> >
> > Before C++11 you can't use multiple threads, but the broker and other
> > examples are supposed to work single-threaded in that case so we should
> > find out what's going wrong.
> >
> > Try a new build with `cmake -DBUILD_CPP_03=YES` to tell cmake that you
> want
> > to build in c++-03 compatibility mode. Cmake is supposed to figure that
> out
> > for itself but maybe there's a problem in the compiler detection logic.
> >
> > If it still crashes raise a JIRA at issues.apache.org and attache
> > theCMakeCache.txt file generated by cmake and the output of these
> commands:
> >
> > $ gcc -v
> > $ gdb --batch --quiet -ex "thread apply all bt full" -ex "quit"
> >  
> >
> >
> > > --
> > > Baptiste Robert
> > >
> >
>
>
>
> --
> Baptiste Robert
>

Re: qpid-proton cpp - Broker example segfault

[Baptiste Robert]

Thank you for your answer, It fixed my issues. Maybe it's due to the
partial support of C++11 integrated in GCC 4.6.2.
In the same way, is it possible to build the last qpid-proton version with
OpenSSL 1.0.0 ? Since the 0.19 version I cannot built it, is it possible to
set a cmake variable to make it compliant ?

Thank you,


2018-03-19 15:21 GMT+01:00 Alan Conway :

> On Mon, Mar 19, 2018 at 4:45 AM, Baptiste Robert <
> baptisterober...@gmail.com
> > wrote:
>
> > Hello,
> >
> > I'm having an issue with the broker example. When I run it works, but a
> > soon as I send messages to it I get a segfault. I send messages with the
> > examples simple_send.
> >
> > Note : I compiled the broker with gcc 4.6.2 e.g. without C++11 support,
> and
> > I'm supposing that is the root cause of a lot of my problem with qpid..
> >
>
> Before C++11 you can't use multiple threads, but the broker and other
> examples are supposed to work single-threaded in that case so we should
> find out what's going wrong.
>
> Try a new build with `cmake -DBUILD_CPP_03=YES` to tell cmake that you want
> to build in c++-03 compatibility mode. Cmake is supposed to figure that out
> for itself but maybe there's a problem in the compiler detection logic.
>
> If it still crashes raise a JIRA at issues.apache.org and attache
> theCMakeCache.txt file generated by cmake and the output of these commands:
>
> $ gcc -v
> $ gdb --batch --quiet -ex "thread apply all bt full" -ex "quit"
>  
>
>
> > --
> > Baptiste Robert
> >
>



-- 
Baptiste Robert

Re: qpid-proton cpp - Broker example segfault

[Alan Conway]

On Mon, Mar 19, 2018 at 4:45 AM, Baptiste Robert  wrote:

> Hello,
>
> I'm having an issue with the broker example. When I run it works, but a
> soon as I send messages to it I get a segfault. I send messages with the
> examples simple_send.
>
> Note : I compiled the broker with gcc 4.6.2 e.g. without C++11 support, and
> I'm supposing that is the root cause of a lot of my problem with qpid..
>

Before C++11 you can't use multiple threads, but the broker and other
examples are supposed to work single-threaded in that case so we should
find out what's going wrong.

Try a new build with `cmake -DBUILD_CPP_03=YES` to tell cmake that you want
to build in c++-03 compatibility mode. Cmake is supposed to figure that out
for itself but maybe there's a problem in the compiler detection logic.

If it still crashes raise a JIRA at issues.apache.org and attache
theCMakeCache.txt file generated by cmake and the output of these commands:

$ gcc -v
$ gdb --batch --quiet -ex "thread apply all bt full" -ex "quit"
 


> --
> Baptiste Robert
>

qpid-proton cpp - Broker example segfault

[Baptiste Robert]

Hello,

I'm having an issue with the broker example. When I run it works, but a
soon as I send messages to it I get a segfault. I send messages with the
examples simple_send.

Note : I compiled the broker with gcc 4.6.2 e.g. without C++11 support, and
I'm supposing that is the root cause of a lot of my problem with qpid..

Thank you,

-- 
Baptiste Robert