Re: Deadlock in pn_messenger_stop? (C Qpid Library)
Hi, Frank. I just had the similar problem. In my case I'm trying to call pn_messenger_stop and the thread hangs. I have only one main thread. So, it seems to be a bug. -- View this message in context: http://qpid.2158936.n2.nabble.com/Deadlock-in-pn-messenger-stop-C-Qpid-Library-tp7594142p7594461.html Sent from the Apache Qpid Proton mailing list archive at Nabble.com.
[jira] [Created] (PROTON-342) installing into custom location doesn't work nicely (and is not properly documented)
Gordon Sim created PROTON-342: - Summary: installing into custom location doesn't work nicely (and is not properly documented) Key: PROTON-342 URL: https://issues.apache.org/jira/browse/PROTON-342 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.4 Reporter: Gordon Sim Assignee: Darryl L. Pierce Fix For: 0.5 The README suggests setting -DCMAKE_INSTALL_PREFIX when running cmake, it does not mention setting DESTDIR when invoking make install. If you don't set the DESTDIR on make install it will honour the CMAKE_INSTALL_PREFIX for some parts of the installation (e.g. header files, native libraries, pkg-config file etc) but the python bindings (and I assume other bindings) will still install in the standard location which will fail if you are not running as root. However if you set DESTDIR then this alters the location of the headers, libraries and pkg-config , which now install into $DESTDIR/$CMAKE_INSTALL_PREFIX and the pkg-config file no longer has the correct include or library paths in it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (PROTON-342) installing into custom location doesn't work nicely (and is not properly documented)
[ https://issues.apache.org/jira/browse/PROTON-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692100#comment-13692100 ] Gordon Sim commented on PROTON-342: --- The problem can be mitigated by specifying -DBUILD_PYTHON=OFF -DBUILD_RUBY=OFF etc when running cmake. This prevents the building and installation of the bindings (and thus avoids having to use DESTDIR at all) installing into custom location doesn't work nicely (and is not properly documented) Key: PROTON-342 URL: https://issues.apache.org/jira/browse/PROTON-342 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.4 Reporter: Gordon Sim Assignee: Darryl L. Pierce Fix For: 0.5 The README suggests setting -DCMAKE_INSTALL_PREFIX when running cmake, it does not mention setting DESTDIR when invoking make install. If you don't set the DESTDIR on make install it will honour the CMAKE_INSTALL_PREFIX for some parts of the installation (e.g. header files, native libraries, pkg-config file etc) but the python bindings (and I assume other bindings) will still install in the standard location which will fail if you are not running as root. However if you set DESTDIR then this alters the location of the headers, libraries and pkg-config , which now install into $DESTDIR/$CMAKE_INSTALL_PREFIX and the pkg-config file no longer has the correct include or library paths in it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (PROTON-342) installing into custom location doesn't work nicely (and is not properly documented)
[ https://issues.apache.org/jira/browse/PROTON-342?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692194#comment-13692194 ] ASF subversion and git services commented on PROTON-342: Commit 1496140 from [~mcpierce] [ https://svn.apache.org/r1496140 ] PROTON-342: Added a note about CMAKE_INSTALL_PREFIX and bindings Explained how it doesn't affect the location for where the language bindings are installed. Also a note about how to use DESTDIR to constrain install locations and how to, from the command line, disable building some or all of the language bindings. installing into custom location doesn't work nicely (and is not properly documented) Key: PROTON-342 URL: https://issues.apache.org/jira/browse/PROTON-342 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.4 Reporter: Gordon Sim Assignee: Darryl L. Pierce Fix For: 0.5 The README suggests setting -DCMAKE_INSTALL_PREFIX when running cmake, it does not mention setting DESTDIR when invoking make install. If you don't set the DESTDIR on make install it will honour the CMAKE_INSTALL_PREFIX for some parts of the installation (e.g. header files, native libraries, pkg-config file etc) but the python bindings (and I assume other bindings) will still install in the standard location which will fail if you are not running as root. However if you set DESTDIR then this alters the location of the headers, libraries and pkg-config , which now install into $DESTDIR/$CMAKE_INSTALL_PREFIX and the pkg-config file no longer has the correct include or library paths in it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (PROTON-342) installing into custom location doesn't work nicely (and is not properly documented)
[ https://issues.apache.org/jira/browse/PROTON-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darryl L. Pierce resolved PROTON-342. - Resolution: Fixed installing into custom location doesn't work nicely (and is not properly documented) Key: PROTON-342 URL: https://issues.apache.org/jira/browse/PROTON-342 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.4 Reporter: Gordon Sim Assignee: Darryl L. Pierce Fix For: 0.5 The README suggests setting -DCMAKE_INSTALL_PREFIX when running cmake, it does not mention setting DESTDIR when invoking make install. If you don't set the DESTDIR on make install it will honour the CMAKE_INSTALL_PREFIX for some parts of the installation (e.g. header files, native libraries, pkg-config file etc) but the python bindings (and I assume other bindings) will still install in the standard location which will fail if you are not running as root. However if you set DESTDIR then this alters the location of the headers, libraries and pkg-config , which now install into $DESTDIR/$CMAKE_INSTALL_PREFIX and the pkg-config file no longer has the correct include or library paths in it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (PROTON-342) installing into custom location doesn't work nicely (and is not properly documented)
[ https://issues.apache.org/jira/browse/PROTON-342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gordon Sim reopened PROTON-342: --- Improving the README is great, but it doesn't resolve the issue (which is that it is not possible to install both c headers/libs and bindings to a non-standard location and still rely on pkg-config for depenency configuration. installing into custom location doesn't work nicely (and is not properly documented) Key: PROTON-342 URL: https://issues.apache.org/jira/browse/PROTON-342 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.4 Reporter: Gordon Sim Assignee: Darryl L. Pierce Fix For: 0.5 The README suggests setting -DCMAKE_INSTALL_PREFIX when running cmake, it does not mention setting DESTDIR when invoking make install. If you don't set the DESTDIR on make install it will honour the CMAKE_INSTALL_PREFIX for some parts of the installation (e.g. header files, native libraries, pkg-config file etc) but the python bindings (and I assume other bindings) will still install in the standard location which will fail if you are not running as root. However if you set DESTDIR then this alters the location of the headers, libraries and pkg-config , which now install into $DESTDIR/$CMAKE_INSTALL_PREFIX and the pkg-config file no longer has the correct include or library paths in it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (PROTON-97) RELEASED disposition not processed by engine
[ https://issues.apache.org/jira/browse/PROTON-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13692260#comment-13692260 ] Rafael H. Schloming commented on PROTON-97: --- What's the extent/consequences of the breakage? I was aware that it was an API change, but I wasn't sure how much that would matter. If there's good reason I could look at trying to maintain more compatibility. Off the top of my head there might be some macro magic we could do, but it would take some exploration to figure out what's possible. RELEASED disposition not processed by engine Key: PROTON-97 URL: https://issues.apache.org/jira/browse/PROTON-97 Project: Qpid Proton Issue Type: Bug Components: proton-c Affects Versions: 0.1 Reporter: Ted Ross Assignee: Rafael H. Schloming Fix For: 0.5 When the proton-c engine receives a disposition with a RELEASED state, it prints a non-log message default 38 in the default clause of a switch (see pn_do_disposition) in engine.c. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
