Re: RC6
Sorry I should have done this before you posted RC6 :( We have a few files (mostly java files) that are missing license headers. Please look at the RAT output I posted. Once the final RC is voted, the release manager (in this case Rafi) will have to sign the final artefacts. You already have your key listed here [1] We should move [1] under the proton main dir. Regards, Rajith [1] https://svn.apache.org/repos/asf/qpid/trunk/qpid/KEYS On Thu, Oct 25, 2012 at 8:38 PM, Rafael Schloming wrote: > I put up an RC6 here[1] with the java shim fixed so the SSL tests skip > properly. That's the only change from RC5. > > [1] http://people.apache.org/~rhs/qpid-proton-0.1rc6/ > > --Rafael
RAT output for Proton
The following RAT output shows that we are missing a few license headers, mostly java files. http://people.apache.org/~rajith/proton/proton-rat-output.txt We need to fix them before releasing. Unfortunately I need to step out now. If somebody hasn't gotten to it by tomorrow morning, I can take care of it. Regards, Rajith P.S There is an option in RAT "-a" that will automatically add the license header. This could potentially mess up cmake files. So be careful :) [1] http://creadur.apache.org/rat/ [2] http://people.apache.org/~rajith/proton/proton-rat-output.txt
RC6
I put up an RC6 here[1] with the java shim fixed so the SSL tests skip properly. That's the only change from RC5. [1] http://people.apache.org/~rhs/qpid-proton-0.1rc6/ --Rafael
RE: [jira] [Created] (PROTON-106) OS X: MSG_NOSIGNAL does not exist
That true for the Visual Studio port too. I had temporarily defined it to 0 to get it to compile. -Original Message- From: Hiram Chirino (JIRA) [mailto:j...@apache.org] Sent: Thursday, October 25, 2012 4:13 PM To: proton@qpid.apache.org Subject: [jira] [Created] (PROTON-106) OS X: MSG_NOSIGNAL does not exist Hiram Chirino created PROTON-106: Summary: OS X: MSG_NOSIGNAL does not exist Key: PROTON-106 URL: https://issues.apache.org/jira/browse/PROTON-106 Project: Qpid Proton Issue Type: Bug Components: proton-c Reporter: Hiram Chirino MSG_NOSIGNAL is used in proton-c/src/driver.c but it does not exist on OS X. -- 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] [Assigned] (PROTON-107) OS X: _POSIX_C_SOURCE is redefined in proton-c/src/ssl/ssl-internal.h
[ https://issues.apache.org/jira/browse/PROTON-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming reassigned PROTON-107: -- Assignee: Rafael H. Schloming > OS X: _POSIX_C_SOURCE is redefined in proton-c/src/ssl/ssl-internal.h > - > > Key: PROTON-107 > URL: https://issues.apache.org/jira/browse/PROTON-107 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Reporter: Hiram Chirino >Assignee: Rafael H. Schloming > > This causes a build failure.. I got around the problem by changing the > define in ssl-internal.h to: > #ifndef _POSIX_C_SOURCE > #define _POSIX_C_SOURCE 1 > #endif -- 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-107) OS X: _POSIX_C_SOURCE is redefined in proton-c/src/ssl/ssl-internal.h
[ https://issues.apache.org/jira/browse/PROTON-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming resolved PROTON-107. Resolution: Fixed > OS X: _POSIX_C_SOURCE is redefined in proton-c/src/ssl/ssl-internal.h > - > > Key: PROTON-107 > URL: https://issues.apache.org/jira/browse/PROTON-107 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Reporter: Hiram Chirino > > This causes a build failure.. I got around the problem by changing the > define in ssl-internal.h to: > #ifndef _POSIX_C_SOURCE > #define _POSIX_C_SOURCE 1 > #endif -- 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
Re: RC5
This was my bad, I'll post an RC6 with the shim fixed. --Rafael On Thu, Oct 25, 2012 at 5:35 PM, Rajith Attapattu wrote: > We have a build failure on the java side. > It appears the SSL tests added in Kens fix is failing. > proton_tests.ssl.SslTest.test_client_authentication . > fail > > We should exclude this test before we spin the final release. > > Rajith > > On Thu, Oct 25, 2012 at 5:25 PM, Ken Giusti wrote: > > mea culpa - apologies. > > > > However, RC5 looks pretty good on these platforms: > > > > Fedora 17 (64bit) > > Debian 6 (32bit, vm) > > Ubuntu 12.04 (32bit, vm) > > Centos 6 (64bit, vm) > > > > > > I simply did a make & install, then ran the proton test suite. A few > warnings during build, but all tests pass. > > > > The only problem platform was my Centos5 VM (32bit). The "make all/make > install" failed due to the php.swg file not being present. It appears that > the version of swig on Centos5 (1.3.29) does not include that php.swg file: > > > > [ 95%] Swig source > > /home/kgiusti/work/proton/RC1/qpid-proton-c-0.1/bindings/php/php.i:4: > Error: Unable to find 'php.swg' > > make[2]: *** [bindings/php/phpPHP_wrap.c] Error 1 > > make[1]: *** [bindings/php/CMakeFiles/cproton.dir/all] Error 2 > > make: *** [all] Error 2 > > > > > > IMHO: +1 RC5, fix the Centos 5 issue in the next release. > > > > -K > > > > - Original Message - > >> Please have a look. This one includes ken's ssl fix in addition to > >> everything that was in RC4: > >> > >> http://people.apache.org/~rhs/qpid-proton-0.1rc5/ > >> >
Re: RC5
That particular test does a DNS lookup on an invalid address, and if that
happens to take a while it can fail the way you're seeing. It will also
fail if you happen to be on one of those networks that are configured to
resolve all invalid hostnames to some kind of search engine.
--Rafael
On Thu, Oct 25, 2012 at 6:56 PM, Rob Godfrey wrote:
> OK - proton-c built OK for me on Ubuntu 12.04 (32-bit) and Centos 6.3
> (32 bit)... Tests all worked fine on the Ubuntu machine. On CentOS I
> got the following error:
>
> proton_tests.messenger.MessengerTest.testSendBogus
>
> ...
> start
> server timed out
> proton_tests.messenger.MessengerTest.testSendBogus
>
> ...
> fail
> Error during teardown: Traceback (most recent call last):
> File "./proton-test", line 331, in run
> phase()
> File "/home/rob/qpid-proton-c-0.1/tests/proton_tests/messenger.py",
> line 45, in teardown
> self.client.send()
> File "/home/rob/qpid-proton-c-0.1/bindings/python/proton.py", line
> 288, in send
> self._check(pn_messenger_send(self._mng))
> File "/home/rob/qpid-proton-c-0.1/bindings/python/proton.py", line
> 149, in _check
> raise exc("[%s]: %s" % (err, pn_messenger_error(self._mng)))
> Timeout: [-7]: unable to send to address: totally-bogus-address
> (getaddrinfo: Name or service not known)
>
> all other tests passed
>
> -- Rob
>
> On 25 October 2012 22:07, Rafael Schloming wrote:
> > Please have a look. This one includes ken's ssl fix in addition to
> > everything that was in RC4:
> >
> > http://people.apache.org/~rhs/qpid-proton-0.1rc5/
>
Re: RC5
OK - proton-c built OK for me on Ubuntu 12.04 (32-bit) and Centos 6.3
(32 bit)... Tests all worked fine on the Ubuntu machine. On CentOS I
got the following error:
proton_tests.messenger.MessengerTest.testSendBogus
...
start
server timed out
proton_tests.messenger.MessengerTest.testSendBogus
...
fail
Error during teardown: Traceback (most recent call last):
File "./proton-test", line 331, in run
phase()
File "/home/rob/qpid-proton-c-0.1/tests/proton_tests/messenger.py",
line 45, in teardown
self.client.send()
File "/home/rob/qpid-proton-c-0.1/bindings/python/proton.py", line
288, in send
self._check(pn_messenger_send(self._mng))
File "/home/rob/qpid-proton-c-0.1/bindings/python/proton.py", line
149, in _check
raise exc("[%s]: %s" % (err, pn_messenger_error(self._mng)))
Timeout: [-7]: unable to send to address: totally-bogus-address
(getaddrinfo: Name or service not known)
all other tests passed
-- Rob
On 25 October 2012 22:07, Rafael Schloming wrote:
> Please have a look. This one includes ken's ssl fix in addition to
> everything that was in RC4:
>
> http://people.apache.org/~rhs/qpid-proton-0.1rc5/
Re: RC5
We have a build failure on the java side. It appears the SSL tests added in Kens fix is failing. proton_tests.ssl.SslTest.test_client_authentication . fail We should exclude this test before we spin the final release. Rajith On Thu, Oct 25, 2012 at 5:25 PM, Ken Giusti wrote: > mea culpa - apologies. > > However, RC5 looks pretty good on these platforms: > > Fedora 17 (64bit) > Debian 6 (32bit, vm) > Ubuntu 12.04 (32bit, vm) > Centos 6 (64bit, vm) > > > I simply did a make & install, then ran the proton test suite. A few > warnings during build, but all tests pass. > > The only problem platform was my Centos5 VM (32bit). The "make all/make > install" failed due to the php.swg file not being present. It appears that > the version of swig on Centos5 (1.3.29) does not include that php.swg file: > > [ 95%] Swig source > /home/kgiusti/work/proton/RC1/qpid-proton-c-0.1/bindings/php/php.i:4: Error: > Unable to find 'php.swg' > make[2]: *** [bindings/php/phpPHP_wrap.c] Error 1 > make[1]: *** [bindings/php/CMakeFiles/cproton.dir/all] Error 2 > make: *** [all] Error 2 > > > IMHO: +1 RC5, fix the Centos 5 issue in the next release. > > -K > > - Original Message - >> Please have a look. This one includes ken's ssl fix in addition to >> everything that was in RC4: >> >> http://people.apache.org/~rhs/qpid-proton-0.1rc5/ >>
Re: RC5
mea culpa - apologies. However, RC5 looks pretty good on these platforms: Fedora 17 (64bit) Debian 6 (32bit, vm) Ubuntu 12.04 (32bit, vm) Centos 6 (64bit, vm) I simply did a make & install, then ran the proton test suite. A few warnings during build, but all tests pass. The only problem platform was my Centos5 VM (32bit). The "make all/make install" failed due to the php.swg file not being present. It appears that the version of swig on Centos5 (1.3.29) does not include that php.swg file: [ 95%] Swig source /home/kgiusti/work/proton/RC1/qpid-proton-c-0.1/bindings/php/php.i:4: Error: Unable to find 'php.swg' make[2]: *** [bindings/php/phpPHP_wrap.c] Error 1 make[1]: *** [bindings/php/CMakeFiles/cproton.dir/all] Error 2 make: *** [all] Error 2 IMHO: +1 RC5, fix the Centos 5 issue in the next release. -K - Original Message - > Please have a look. This one includes ken's ssl fix in addition to > everything that was in RC4: > > http://people.apache.org/~rhs/qpid-proton-0.1rc5/ >
[jira] [Updated] (PROTON-105) OS X: Build has warnings, cause build failures
[ https://issues.apache.org/jira/browse/PROTON-105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino updated PROTON-105: - Component/s: proton-c > OS X: Build has warnings, cause build failures > -- > > Key: PROTON-105 > URL: https://issues.apache.org/jira/browse/PROTON-105 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Reporter: Hiram Chirino > > Perhaps you '-Werror -pedantic-errors' should be removed from the build > options for the OS X build. -- 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] [Created] (PROTON-108) OS X: PHP libs not linked
Hiram Chirino created PROTON-108: Summary: OS X: PHP libs not linked Key: PROTON-108 URL: https://issues.apache.org/jira/browse/PROTON-108 Project: Qpid Proton Issue Type: Bug Components: proton-c Reporter: Hiram Chirino gcc command run was: /usr/bin/gcc-bundle -Wl,-headerpad_max_install_names -o cproton.so CMakeFiles/cproton.dir/phpPHP_wrap.c.o ../../libqpid-proton.dylib /usr/lib/libssl.dylib /usr/lib/libcrypto.dylib results in the following failures: https://gist.github.com/b14d9243bd3d5715f60e -- 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] [Updated] (PROTON-107) OS X: _POSIX_C_SOURCE is redefined in proton-c/src/ssl/ssl-internal.h
[ https://issues.apache.org/jira/browse/PROTON-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino updated PROTON-107: - Component/s: proton-c > OS X: _POSIX_C_SOURCE is redefined in proton-c/src/ssl/ssl-internal.h > - > > Key: PROTON-107 > URL: https://issues.apache.org/jira/browse/PROTON-107 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Reporter: Hiram Chirino > > This causes a build failure.. I got around the problem by changing the > define in ssl-internal.h to: > #ifndef _POSIX_C_SOURCE > #define _POSIX_C_SOURCE 1 > #endif -- 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] [Updated] (PROTON-104) OS X: Don't link uuid
[ https://issues.apache.org/jira/browse/PROTON-104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino updated PROTON-104: - Component/s: proton-c > OS X: Don't link uuid > - > > Key: PROTON-104 > URL: https://issues.apache.org/jira/browse/PROTON-104 > Project: Qpid Proton > Issue Type: Bug > Components: proton-c >Reporter: Hiram Chirino > > Don't link uuid lib on OX, it does not exist / is part the clib. -- 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] [Created] (PROTON-107) OS X: _POSIX_C_SOURCE is redefined in proton-c/src/ssl/ssl-internal.h
Hiram Chirino created PROTON-107: Summary: OS X: _POSIX_C_SOURCE is redefined in proton-c/src/ssl/ssl-internal.h Key: PROTON-107 URL: https://issues.apache.org/jira/browse/PROTON-107 Project: Qpid Proton Issue Type: Bug Reporter: Hiram Chirino This causes a build failure.. I got around the problem by changing the define in ssl-internal.h to: #ifndef _POSIX_C_SOURCE #define _POSIX_C_SOURCE 1 #endif -- 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] [Created] (PROTON-106) OS X: MSG_NOSIGNAL does not exist
Hiram Chirino created PROTON-106: Summary: OS X: MSG_NOSIGNAL does not exist Key: PROTON-106 URL: https://issues.apache.org/jira/browse/PROTON-106 Project: Qpid Proton Issue Type: Bug Components: proton-c Reporter: Hiram Chirino MSG_NOSIGNAL is used in proton-c/src/driver.c but it does not exist on OS X. -- 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] [Created] (PROTON-105) OS X: Build has warnings, cause build failures
Hiram Chirino created PROTON-105: Summary: OS X: Build has warnings, cause build failures Key: PROTON-105 URL: https://issues.apache.org/jira/browse/PROTON-105 Project: Qpid Proton Issue Type: Bug Reporter: Hiram Chirino Perhaps you '-Werror -pedantic-errors' should be removed from the build options for the OS X build. -- 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] [Created] (PROTON-104) OS X: Don't link uuid
Hiram Chirino created PROTON-104: Summary: OS X: Don't link uuid Key: PROTON-104 URL: https://issues.apache.org/jira/browse/PROTON-104 Project: Qpid Proton Issue Type: Bug Reporter: Hiram Chirino Don't link uuid lib on OX, it does not exist / is part the clib. -- 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
RC5
Please have a look. This one includes ken's ssl fix in addition to everything that was in RC4: http://people.apache.org/~rhs/qpid-proton-0.1rc5/
Re: RC4
Ok, I'm -1ing this one because ken's ssl fix didn't make it in. Sorry for the churn. RC5 will be up shortly with ken's ssl fix in it. --Rafael On Thu, Oct 25, 2012 at 1:42 PM, Rafael Schloming wrote: > I've posted an RC4 here: > > http://people.apache.org/~rhs/qpid-proton-0.1rc4/ > > I believe both the koji issue and the decimal64 issue should be fixed now. > > The full changelog from the previous RC is here: > > > r1402224 | rhs | 2012-10-25 13:29:14 -0400 (Thu, 25 Oct 2012) | 1 line > > gracefully skip ssl tests when ssl is not built > > r1402223 | mcpierce | 2012-10-25 13:16:49 -0400 (Thu, 25 Oct 2012) | 1 line > > NO-JIRA: Removes the path from the usage filename displayed for proton. > > r1402221 | rhs | 2012-10-25 13:09:48 -0400 (Thu, 25 Oct 2012) | 1 line > > fixed swig interface typedefs > > r1402217 | rgodfrey | 2012-10-25 13:00:37 -0400 (Thu, 25 Oct 2012) | 1 line > > PROTON-103 : Implement SASL in proton-j > > r1402184 | kgiusti | 2012-10-25 11:01:06 -0400 (Thu, 25 Oct 2012) | 1 line > > NO-JIRA: fix warnings for swig code on older linux > > r1402141 | kgiusti | 2012-10-25 09:11:29 -0400 (Thu, 25 Oct 2012) | 1 line > > NO-JIRA: fix macro name collision > > r1402100 | rhs | 2012-10-25 06:57:27 -0400 (Thu, 25 Oct 2012) | 1 line > > don't ignore the return value of write > > r1402079 | rhs | 2012-10-25 06:12:46 -0400 (Thu, 25 Oct 2012) | 1 line > > tweaked the README language > > r1401959 | rajith | 2012-10-24 22:55:17 -0400 (Wed, 24 Oct 2012) | 2 lines > > PROTON-66 We now register for WRITE_OP if we are unable to write to the > channel. As soon we are successful in writing we deregister the WRITE_OP. > >
[jira] [Resolved] (PROTON-102) config.sh fails on OS X
[ https://issues.apache.org/jira/browse/PROTON-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rafael H. Schloming resolved PROTON-102. Resolution: Fixed > config.sh fails on OS X > --- > > Key: PROTON-102 > URL: https://issues.apache.org/jira/browse/PROTON-102 > Project: Qpid Proton > Issue Type: Bug >Reporter: Hiram Chirino > Attachments: PROTON-102.patch > > -- 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
RC4
I've posted an RC4 here: http://people.apache.org/~rhs/qpid-proton-0.1rc4/ I believe both the koji issue and the decimal64 issue should be fixed now. The full changelog from the previous RC is here: r1402224 | rhs | 2012-10-25 13:29:14 -0400 (Thu, 25 Oct 2012) | 1 line gracefully skip ssl tests when ssl is not built r1402223 | mcpierce | 2012-10-25 13:16:49 -0400 (Thu, 25 Oct 2012) | 1 line NO-JIRA: Removes the path from the usage filename displayed for proton. r1402221 | rhs | 2012-10-25 13:09:48 -0400 (Thu, 25 Oct 2012) | 1 line fixed swig interface typedefs r1402217 | rgodfrey | 2012-10-25 13:00:37 -0400 (Thu, 25 Oct 2012) | 1 line PROTON-103 : Implement SASL in proton-j r1402184 | kgiusti | 2012-10-25 11:01:06 -0400 (Thu, 25 Oct 2012) | 1 line NO-JIRA: fix warnings for swig code on older linux r1402141 | kgiusti | 2012-10-25 09:11:29 -0400 (Thu, 25 Oct 2012) | 1 line NO-JIRA: fix macro name collision r1402100 | rhs | 2012-10-25 06:57:27 -0400 (Thu, 25 Oct 2012) | 1 line don't ignore the return value of write r1402079 | rhs | 2012-10-25 06:12:46 -0400 (Thu, 25 Oct 2012) | 1 line tweaked the README language r1401959 | rajith | 2012-10-24 22:55:17 -0400 (Wed, 24 Oct 2012) | 2 lines PROTON-66 We now register for WRITE_OP if we are unable to write to the channel. As soon we are successful in writing we deregister the WRITE_OP.
Re: RC3
On Thu, Oct 25, 2012 at 11:14:06AM -0400, Rafael Schloming wrote: > I've fixed the ignored write value on trunk, but I suspect you're somehow > building with a different set of compiler flags as I don't see this issue > when I build on f17 myself. You can try the next RC, but there may other > problems if the flags you're building with don't match what we've been > developing the code with. I've pulled out that patch and the filename fix for the proton executable and am doing a scratch build in koji now. http://koji.fedoraproject.org/koji/taskinfo?taskID=4626398 Success. -- Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/ pgpg6tUjm0quh.pgp Description: PGP signature
[jira] [Resolved] (PROTON-103) [Proton-j] Add SASL support
[ https://issues.apache.org/jira/browse/PROTON-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rob Godfrey resolved PROTON-103. Resolution: Fixed > [Proton-j] Add SASL support > --- > > Key: PROTON-103 > URL: https://issues.apache.org/jira/browse/PROTON-103 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j >Affects Versions: 0.1 >Reporter: Rob Godfrey >Assignee: Rob Godfrey > Fix For: 0.2 > > > Implement the SASL functionality in proton-j -- 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] [Created] (PROTON-103) [Proton-j] Add SASL support
Rob Godfrey created PROTON-103: -- Summary: [Proton-j] Add SASL support Key: PROTON-103 URL: https://issues.apache.org/jira/browse/PROTON-103 Project: Qpid Proton Issue Type: Bug Components: proton-j Affects Versions: 0.1 Reporter: Rob Godfrey Assignee: Rob Godfrey Fix For: 0.2 Implement the SASL functionality in proton-j -- 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] [Updated] (PROTON-102) config.sh fails on OS X
[ https://issues.apache.org/jira/browse/PROTON-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hiram Chirino updated PROTON-102: - Attachment: PROTON-102.patch attaching patch that fixes the issue on OS X > config.sh fails on OS X > --- > > Key: PROTON-102 > URL: https://issues.apache.org/jira/browse/PROTON-102 > Project: Qpid Proton > Issue Type: Bug >Reporter: Hiram Chirino > Attachments: PROTON-102.patch > > -- 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] [Created] (PROTON-102) config.sh fails on OS X
Hiram Chirino created PROTON-102: Summary: config.sh fails on OS X Key: PROTON-102 URL: https://issues.apache.org/jira/browse/PROTON-102 Project: Qpid Proton Issue Type: Bug Reporter: Hiram Chirino -- 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-102) config.sh fails on OS X
[ https://issues.apache.org/jira/browse/PROTON-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13484216#comment-13484216 ] Hiram Chirino commented on PROTON-102: -- $ . config.sh readlink: illegal option -- f usage: readlink [-n] [file ...] usage: dirname path > config.sh fails on OS X > --- > > Key: PROTON-102 > URL: https://issues.apache.org/jira/browse/PROTON-102 > Project: Qpid Proton > Issue Type: Bug >Reporter: Hiram Chirino > -- 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
RE: RC3
I don't know if the new file libgen.h will cause any new porting problems
yet with Visual Studio compilers.
I'm still working off older code.
It will probably need an #ifdef in the proton.c file for the Windows port.
If it's only added to proton.c, it should only be a minor problem for the
Windows port.
-Original Message-
From: Rafael Schloming [mailto:r...@alum.mit.edu]
Sent: Thursday, October 25, 2012 11:11 AM
To: proton@qpid.apache.org
Subject: Re: RC3
Ok, go ahead as long as it doesn't make things worse wrt windows porting.
--Rafael
On Thu, Oct 25, 2012 at 11:05 AM, Mary Hinton wrote:
> libgen.h - definitions for pattern matching functions
>
> Some of the other proton headers that are being used now are not part
> of the Visual Studio compiler header files I've been doing #ifdef (s)
> around the header files. E.g.
> #include
> #include
>
> -Original Message-
> From: Rafael Schloming [mailto:r...@alum.mit.edu]
> Sent: Thursday, October 25, 2012 10:49 AM
> To: proton@qpid.apache.org
> Subject: Re: RC3
>
> What's libgen.h? Is that available on windows?
>
> --Rafael
>
> On Thu, Oct 25, 2012 at 10:38 AM, Darryl L. Pierce
> wrote:
>
> > On Wed, Oct 24, 2012 at 03:29:44PM -0400, Rafael Schloming wrote:
> > > I've put up an RC3 here:
> > >
> > > http://people.apache.org/~rhs/qpid-proton-0.1rc3/
> > >
> > > The following are the changes from RC2:
> > >
> > > - added README and LICENSE for proton-j
> > > - updated the proton-c README
> > > - fixed cmake build to not use the OPTIONAL thing for older versions
> > > - fixed detection of LIB_SUFFIX (i.e. we won't install into
> > > lib64 on 32 bit systems anymore)
> >
> > I have a small fix for the proton binary that removes the pathname
> > for the binary in the usage output:
> >
> > diff --git a/proton-c/src/proton.c b/proton-c/src/proton.c index
> > 0473fdf..0969538 100644
> > --- a/proton-c/src/proton.c
> > +++ b/proton-c/src/proton.c
> > @@ -27,6 +27,7 @@
> > #include
> > #include
> > #include
> > +#include
> > #include "util.h"
> > #include "pn_config.h"
> > #include
> > @@ -426,7 +427,7 @@ int main(int argc, char **argv)
> >buffer(argc, argv);
> >exit(EXIT_SUCCESS);
> > case 'h':
> > - printf("Usage: %s [-h] [-c [user[:password]@]host[:port]] [-a
> >] [-m ]\n", argv[0]);
> > + printf("Usage: %s [-h] [-c [user[:password]@]host[:port]] [-a
> > ] [-m ]\n", basename(argv[0]));
> >printf("\n");
> >printf("-cThe connect url.\n");
> >printf("-aThe AMQP address.\n");
> >
> > I'd like to commit this to keep the hostname from showing up in
> > packaged binaries.
> >
> > --
> > Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
> > Delivering value year after year.
> > Red Hat ranks #1 in value among software vendors.
> > http://www.redhat.com/promo/vendor/
> >
> >
>
>
>
Re: RC3
I've fixed the ignored write value on trunk, but I suspect you're somehow building with a different set of compiler flags as I don't see this issue when I build on f17 myself. You can try the next RC, but there may other problems if the flags you're building with don't match what we've been developing the code with. --Rafael On Wed, Oct 24, 2012 at 5:01 PM, Darryl L. Pierce wrote: > On Wed, Oct 24, 2012 at 10:24:47PM +0200, Rob Godfrey wrote: > > I got the following failure on proton-c from this release on 32-bit > > Ubuntu 12.04: > > And I'm still failing on the package build with: > > /home/mcpierce/Packaging/rpms/BUILD/qpid-proton-c-0.1/src/driver.c: In > function 'pn_driver_wakeup': > /home/mcpierce/Packaging/rpms/BUILD/qpid-proton-c-0.1/src/driver.c:673:5: > error: ignoring return value of 'write', declared with attribute > warn_unused_result [-Werror=unused-result] > cc1: all warnings being treated as errors > make[2]: *** [CMakeFiles/qpid-proton.dir/src/driver.c.o] Error 1 > make[2]: *** Waiting for unfinished jobs > make[2]: Leaving directory > `/home/mcpierce/Packaging/rpms/BUILD/qpid-proton-c-0.1' > make[1]: *** [CMakeFiles/qpid-proton.dir/all] Error 2 > make[1]: Leaving directory > `/home/mcpierce/Packaging/rpms/BUILD/qpid-proton-c-0.1' > make: *** [all] Error 2 > error: Bad exit status from > /home/mcpierce/Packaging/rpms/tmp/rpm-tmp.pJTeSb (%build) > > > -- > Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. > Delivering value year after year. > Red Hat ranks #1 in value among software vendors. > http://www.redhat.com/promo/vendor/ > >
Re: RC3
Ok, go ahead as long as it doesn't make things worse wrt windows porting.
--Rafael
On Thu, Oct 25, 2012 at 11:05 AM, Mary Hinton wrote:
> libgen.h - definitions for pattern matching functions
>
> Some of the other proton headers that are being used now are not part of
> the
> Visual Studio compiler header files
> I've been doing #ifdef (s) around the header files. E.g.
> #include
> #include
>
> -Original Message-
> From: Rafael Schloming [mailto:r...@alum.mit.edu]
> Sent: Thursday, October 25, 2012 10:49 AM
> To: proton@qpid.apache.org
> Subject: Re: RC3
>
> What's libgen.h? Is that available on windows?
>
> --Rafael
>
> On Thu, Oct 25, 2012 at 10:38 AM, Darryl L. Pierce
> wrote:
>
> > On Wed, Oct 24, 2012 at 03:29:44PM -0400, Rafael Schloming wrote:
> > > I've put up an RC3 here:
> > >
> > > http://people.apache.org/~rhs/qpid-proton-0.1rc3/
> > >
> > > The following are the changes from RC2:
> > >
> > > - added README and LICENSE for proton-j
> > > - updated the proton-c README
> > > - fixed cmake build to not use the OPTIONAL thing for older versions
> > > - fixed detection of LIB_SUFFIX (i.e. we won't install into lib64
> > > on 32 bit systems anymore)
> >
> > I have a small fix for the proton binary that removes the pathname for
> > the binary in the usage output:
> >
> > diff --git a/proton-c/src/proton.c b/proton-c/src/proton.c index
> > 0473fdf..0969538 100644
> > --- a/proton-c/src/proton.c
> > +++ b/proton-c/src/proton.c
> > @@ -27,6 +27,7 @@
> > #include
> > #include
> > #include
> > +#include
> > #include "util.h"
> > #include "pn_config.h"
> > #include
> > @@ -426,7 +427,7 @@ int main(int argc, char **argv)
> >buffer(argc, argv);
> >exit(EXIT_SUCCESS);
> > case 'h':
> > - printf("Usage: %s [-h] [-c [user[:password]@]host[:port]] [-a
> >] [-m ]\n", argv[0]);
> > + printf("Usage: %s [-h] [-c [user[:password]@]host[:port]] [-a
> > ] [-m ]\n", basename(argv[0]));
> >printf("\n");
> >printf("-cThe connect url.\n");
> >printf("-aThe AMQP address.\n");
> >
> > I'd like to commit this to keep the hostname from showing up in
> > packaged binaries.
> >
> > --
> > Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
> > Delivering value year after year.
> > Red Hat ranks #1 in value among software vendors.
> > http://www.redhat.com/promo/vendor/
> >
> >
>
>
>
RE: RC3
libgen.h - definitions for pattern matching functions
Some of the other proton headers that are being used now are not part of the
Visual Studio compiler header files
I've been doing #ifdef (s) around the header files. E.g.
#include
#include
-Original Message-
From: Rafael Schloming [mailto:r...@alum.mit.edu]
Sent: Thursday, October 25, 2012 10:49 AM
To: proton@qpid.apache.org
Subject: Re: RC3
What's libgen.h? Is that available on windows?
--Rafael
On Thu, Oct 25, 2012 at 10:38 AM, Darryl L. Pierce
wrote:
> On Wed, Oct 24, 2012 at 03:29:44PM -0400, Rafael Schloming wrote:
> > I've put up an RC3 here:
> >
> > http://people.apache.org/~rhs/qpid-proton-0.1rc3/
> >
> > The following are the changes from RC2:
> >
> > - added README and LICENSE for proton-j
> > - updated the proton-c README
> > - fixed cmake build to not use the OPTIONAL thing for older versions
> > - fixed detection of LIB_SUFFIX (i.e. we won't install into lib64
> > on 32 bit systems anymore)
>
> I have a small fix for the proton binary that removes the pathname for
> the binary in the usage output:
>
> diff --git a/proton-c/src/proton.c b/proton-c/src/proton.c index
> 0473fdf..0969538 100644
> --- a/proton-c/src/proton.c
> +++ b/proton-c/src/proton.c
> @@ -27,6 +27,7 @@
> #include
> #include
> #include
> +#include
> #include "util.h"
> #include "pn_config.h"
> #include
> @@ -426,7 +427,7 @@ int main(int argc, char **argv)
>buffer(argc, argv);
>exit(EXIT_SUCCESS);
> case 'h':
> - printf("Usage: %s [-h] [-c [user[:password]@]host[:port]] [-a
>] [-m ]\n", argv[0]);
> + printf("Usage: %s [-h] [-c [user[:password]@]host[:port]] [-a
> ] [-m ]\n", basename(argv[0]));
>printf("\n");
>printf("-cThe connect url.\n");
>printf("-aThe AMQP address.\n");
>
> I'd like to commit this to keep the hostname from showing up in
> packaged binaries.
>
> --
> Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
> Delivering value year after year.
> Red Hat ranks #1 in value among software vendors.
> http://www.redhat.com/promo/vendor/
>
>
Re: RC3
On Thu, Oct 25, 2012 at 10:49:24AM -0400, Rafael Schloming wrote: > What's libgen.h? Is that available on windows? libgen.h is provided by glibc-headers and is a part of the POSIX standard, providing the basename() API used. -- Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/ pgpLTfgz6mqGi.pgp Description: PGP signature
Re: RC3
What's libgen.h? Is that available on windows?
--Rafael
On Thu, Oct 25, 2012 at 10:38 AM, Darryl L. Pierce wrote:
> On Wed, Oct 24, 2012 at 03:29:44PM -0400, Rafael Schloming wrote:
> > I've put up an RC3 here:
> >
> > http://people.apache.org/~rhs/qpid-proton-0.1rc3/
> >
> > The following are the changes from RC2:
> >
> > - added README and LICENSE for proton-j
> > - updated the proton-c README
> > - fixed cmake build to not use the OPTIONAL thing for older versions
> > - fixed detection of LIB_SUFFIX (i.e. we won't install into lib64 on 32
> > bit systems anymore)
>
> I have a small fix for the proton binary that removes the pathname for
> the binary in the usage output:
>
> diff --git a/proton-c/src/proton.c b/proton-c/src/proton.c
> index 0473fdf..0969538 100644
> --- a/proton-c/src/proton.c
> +++ b/proton-c/src/proton.c
> @@ -27,6 +27,7 @@
> #include
> #include
> #include
> +#include
> #include "util.h"
> #include "pn_config.h"
> #include
> @@ -426,7 +427,7 @@ int main(int argc, char **argv)
>buffer(argc, argv);
>exit(EXIT_SUCCESS);
> case 'h':
> - printf("Usage: %s [-h] [-c [user[:password]@]host[:port]] [-a
>] [-m ]\n", argv[0]);
> + printf("Usage: %s [-h] [-c [user[:password]@]host[:port]] [-a
> ] [-m ]\n", basename(argv[0]));
>printf("\n");
>printf("-cThe connect url.\n");
>printf("-aThe AMQP address.\n");
>
> I'd like to commit this to keep the hostname from showing up in packaged
> binaries.
>
> --
> Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
> Delivering value year after year.
> Red Hat ranks #1 in value among software vendors.
> http://www.redhat.com/promo/vendor/
>
>
Re: RC3
On Wed, Oct 24, 2012 at 03:29:44PM -0400, Rafael Schloming wrote:
> I've put up an RC3 here:
>
> http://people.apache.org/~rhs/qpid-proton-0.1rc3/
>
> The following are the changes from RC2:
>
> - added README and LICENSE for proton-j
> - updated the proton-c README
> - fixed cmake build to not use the OPTIONAL thing for older versions
> - fixed detection of LIB_SUFFIX (i.e. we won't install into lib64 on 32
> bit systems anymore)
I have a small fix for the proton binary that removes the pathname for
the binary in the usage output:
diff --git a/proton-c/src/proton.c b/proton-c/src/proton.c
index 0473fdf..0969538 100644
--- a/proton-c/src/proton.c
+++ b/proton-c/src/proton.c
@@ -27,6 +27,7 @@
#include
#include
#include
+#include
#include "util.h"
#include "pn_config.h"
#include
@@ -426,7 +427,7 @@ int main(int argc, char **argv)
buffer(argc, argv);
exit(EXIT_SUCCESS);
case 'h':
- printf("Usage: %s [-h] [-c [user[:password]@]host[:port]] [-a
] [-m ]\n", argv[0]);
+ printf("Usage: %s [-h] [-c [user[:password]@]host[:port]] [-a
] [-m ]\n", basename(argv[0]));
printf("\n");
printf("-cThe connect url.\n");
printf("-aThe AMQP address.\n");
I'd like to commit this to keep the hostname from showing up in packaged
binaries.
--
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
pgp0LYWu3amoZ.pgp
Description: PGP signature
Re: RC3
Can you dig out the generated swig code from your build tree and post the snippet being referenced? --Rafael On Thu, Oct 25, 2012 at 9:15 AM, Ken Giusti wrote: > Fix committed for NAME_MAX. > > But now this on trunk as well as RC3 (again Centos5 x64): > > > [ 91%] Building C object > bindings/python/CMakeFiles/_cproton.dir/pythonPYTHON_wrap.c.o > /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c: > In function ‘wrap_pn_connector_set_context’: > /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c:2842: > warning: dereferencing ‘void *’ pointer > /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c:2842: > error: request for member ‘ob_refcnt’ in something not a structure or union > /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c: > In function ‘wrap_pn_connection_set_context’: > /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c:2867: > warning: dereferencing ‘void *’ pointer > /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c:2867: > error: request for member ‘ob_refcnt’ in something not a structure or union > /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c: > In function ‘wrap_pn_session_set_context’: > /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c:2892: > warning: dereferencing ‘void *’ pointer > /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c:2892: > error: request for member ‘ob_refcnt’ in something not a structure or union > /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c: > In function ‘wrap_pn_link_set_context’: > /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c:2917: > warning: dereferencing ‘void *’ pointer > /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c:2917: > error: request for member ‘ob_refcnt’ in something not a structure or union > /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c: > In function ‘wrap_pn_delivery_set_context’: > /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c:2942: > warning: dereferencing ‘void *’ pointer > /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c:2942: > error: request for member ‘ob_refcnt’ in something not a structure or union > make[2]: *** > [bindings/python/CMakeFiles/_cproton.dir/pythonPYTHON_wrap.c.o] Error 1 > make[1]: *** [bindings/python/CMakeFiles/_cproton.dir/all] Error 2 > make: *** [all] Error 2 > [kgiusti@centos5 build]$ > > -K > > - Original Message - > > Centos5 x64 build failure - funny didn't I see this before? > > > > [ 69%] Building C object CMakeFiles/qpid-proton.dir/src/driver.c.o > > /home/kgiusti/proton/qpid-proton-c-0.1/src/driver.c:75:1: error: > > "NAME_MAX" redefined > > In file included from /usr/include/bits/local_lim.h:36, > > from /usr/include/bits/posix1_lim.h:153, > > from /usr/include/limits.h:145, > > from > > > /usr/lib/gcc/x86_64-redhat-linux/4.1.2/include/limits.h:122, > > from > > > /usr/lib/gcc/x86_64-redhat-linux/4.1.2/include/syslimits.h:7, > > from > > > /usr/lib/gcc/x86_64-redhat-linux/4.1.2/include/limits.h:11, > > from /usr/include/bits/socket.h:31, > > from /usr/include/sys/socket.h:35, > > from > > /home/kgiusti/proton/qpid-proton-c-0.1/src/driver.c:29: > > /usr/include/linux/limits.h:13:1: error: this is the location of the > > previous definition > > make[2]: *** [CMakeFiles/qpid-proton.dir/src/driver.c.o] Error 1 > > make[1]: *** [CMakeFiles/qpid-proton.dir/all] Error 2 > > make: *** [all] Error 2 > > > > > > -K > > > > - Original Message - > > > Are the examples supposed to work for this release? Because the > > > instructions don't tell people how to get them running. I don't see > > > the config.sh file. (I mentioned this in a previous email. I'll log > > > a Jira.) > > > > > > William > > > > > > - Original Message - > > > > I've put up an RC3 here: > > > > > > > > http://people.apache.org/~rhs/qpid-proton-0.1rc3/ > > > > > > > > The following are the changes from RC2: > > > > > > > > - added README and LICENSE for proton-j > > > > - updated the proton-c README > > > > - fixed cmake build to not use the OPTIONAL thing for older > > > > versions > > > > - fixed detection of LIB_SUFFIX (i.e. we won't install into > > > > lib64 > > > > on 32 > > > > bit systems anymore) > > > > > > > > --Rafael > > > > > > > > > >
Re: initial release candidate
On Thu, Oct 25, 2012 at 8:18 AM, Ken Giusti wrote: > The following patch fixes the problem with older versions of the SSL > library. > > It also works on the latest Fedora 17, so I think it's low risk. > > Shall I commit it? > Sure --Rafael
Re: RC3
Fix committed for NAME_MAX. But now this on trunk as well as RC3 (again Centos5 x64): [ 91%] Building C object bindings/python/CMakeFiles/_cproton.dir/pythonPYTHON_wrap.c.o /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c: In function ‘wrap_pn_connector_set_context’: /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c:2842: warning: dereferencing ‘void *’ pointer /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c:2842: error: request for member ‘ob_refcnt’ in something not a structure or union /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c: In function ‘wrap_pn_connection_set_context’: /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c:2867: warning: dereferencing ‘void *’ pointer /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c:2867: error: request for member ‘ob_refcnt’ in something not a structure or union /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c: In function ‘wrap_pn_session_set_context’: /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c:2892: warning: dereferencing ‘void *’ pointer /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c:2892: error: request for member ‘ob_refcnt’ in something not a structure or union /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c: In function ‘wrap_pn_link_set_context’: /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c:2917: warning: dereferencing ‘void *’ pointer /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c:2917: error: request for member ‘ob_refcnt’ in something not a structure or union /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c: In function ‘wrap_pn_delivery_set_context’: /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c:2942: warning: dereferencing ‘void *’ pointer /home/kgiusti/proton/qpid-proton/proton-c/build/bindings/python/pythonPYTHON_wrap.c:2942: error: request for member ‘ob_refcnt’ in something not a structure or union make[2]: *** [bindings/python/CMakeFiles/_cproton.dir/pythonPYTHON_wrap.c.o] Error 1 make[1]: *** [bindings/python/CMakeFiles/_cproton.dir/all] Error 2 make: *** [all] Error 2 [kgiusti@centos5 build]$ -K - Original Message - > Centos5 x64 build failure - funny didn't I see this before? > > [ 69%] Building C object CMakeFiles/qpid-proton.dir/src/driver.c.o > /home/kgiusti/proton/qpid-proton-c-0.1/src/driver.c:75:1: error: > "NAME_MAX" redefined > In file included from /usr/include/bits/local_lim.h:36, > from /usr/include/bits/posix1_lim.h:153, > from /usr/include/limits.h:145, > from > /usr/lib/gcc/x86_64-redhat-linux/4.1.2/include/limits.h:122, > from > /usr/lib/gcc/x86_64-redhat-linux/4.1.2/include/syslimits.h:7, > from > /usr/lib/gcc/x86_64-redhat-linux/4.1.2/include/limits.h:11, > from /usr/include/bits/socket.h:31, > from /usr/include/sys/socket.h:35, > from > /home/kgiusti/proton/qpid-proton-c-0.1/src/driver.c:29: > /usr/include/linux/limits.h:13:1: error: this is the location of the > previous definition > make[2]: *** [CMakeFiles/qpid-proton.dir/src/driver.c.o] Error 1 > make[1]: *** [CMakeFiles/qpid-proton.dir/all] Error 2 > make: *** [all] Error 2 > > > -K > > - Original Message - > > Are the examples supposed to work for this release? Because the > > instructions don't tell people how to get them running. I don't see > > the config.sh file. (I mentioned this in a previous email. I'll log > > a Jira.) > > > > William > > > > - Original Message - > > > I've put up an RC3 here: > > > > > > http://people.apache.org/~rhs/qpid-proton-0.1rc3/ > > > > > > The following are the changes from RC2: > > > > > > - added README and LICENSE for proton-j > > > - updated the proton-c README > > > - fixed cmake build to not use the OPTIONAL thing for older > > > versions > > > - fixed detection of LIB_SUFFIX (i.e. we won't install into > > > lib64 > > > on 32 > > > bit systems anymore) > > > > > > --Rafael > > > > > >
Re: RC3
Thanks. It was ambiguous. Looked like it was optional and had a default (which it did) Now hopefully people can just deduce more info about the examples from the examples/README.txt and PROTON-100 can be ignored ;-) Sent from my iPhone On Oct 25, 2012, at 4:14 AM, Rafael Schloming wrote: > Done. I stopped short of putting "Hey William! Set the install prefix." ;-) > > --Rafael > > On Wed, Oct 24, 2012 at 11:22 PM, William Henry wrote: > >> Change: >> # depending on your system you may want to adjust the install prefix >> cmake -DCMAKE_INSTALL_PREFIX=/usr .. >> >> To: >> # Set the install prefix. You may need to adjust depending on your system >> cmake -DCMAKE_INSTALL_PREFIX=/usr .. >> >> >> - Original Message - >>> It looks like you installed everything into /usr/local. I'm guessing >>> the >>> system python (installed in /usr) does not look under /usr/local as >>> part of >>> it's module search path. Try installing into /usr instead. >>> >>> --Rafael >>> >>> On Wed, Oct 24, 2012 at 10:10 PM, William Henry >>> wrote: >>> $ more build/install_manifest.txt /usr/local/bin/proton /usr/local/bin/proton-dump /usr/local/lib64/libqpid-proton.so /usr/local/include/proton/parser.h /usr/local/include/proton/util.h /usr/local/include/proton/ssl.h /usr/local/include/proton/scanner.h /usr/local/include/proton/cproton.i /usr/local/include/proton/messenger.h /usr/local/include/proton/message.h /usr/local/include/proton/sasl.h /usr/local/include/proton/driver.h /usr/local/include/proton/types.h /usr/local/include/proton/buffer.h /usr/local/include/proton/framing.h /usr/local/include/proton/codec.h /usr/local/include/proton/engine.h /usr/local/include/proton/error.h /usr/local/share/proton/LICENSE /usr/local/share/proton/README /usr/local/share/proton/TODO /usr/local/lib64/pkgconfig/libqpid-proton.pc /usr/local/lib64/python2.7/site-packages/cproton.py /usr/local/lib64/python2.7/site-packages/cproton.pyc /usr/local/lib64/python2.7/site-packages/cproton.pyo /usr/local/lib64/python2.7/site-packages/proton.py /usr/local/lib64/python2.7/site-packages/proton.pyc /usr/local/lib64/python2.7/site-packages/proton.pyo /usr/local/lib64/python2.7/site-packages/_cproton.so /usr/local/lib64/ruby/cproton.so /usr/local/lib64/php/modules/cproton.so /usr/local/share/php/cproton.php /usr/local/share/php/proton.php /etc/php.d/cproton.ini - Original Message - > Can you post the contents of your install_manifest.txt? > > On Wed, Oct 24, 2012 at 9:50 PM, William Henry > > wrote: > >> Ok install was successful. Still have an ImportError for >> proton. >> >> Not sure what I'm missing >> >> William >> >> Sent from my iPhone >> >> On Oct 24, 2012, at 7:29 PM, Rafael Schloming >> >> wrote: >> >>> The examples should work without the config.sh, it just sets >>> up >>> stuff for >>> the dev environment. If you do the make install, all the >>> proton >>> stuff >>> should be available without any special environmental config. >>> >>> --Rafael >>> >>> On Wed, Oct 24, 2012 at 8:11 PM, William Henry >>> >> wrote: >>> Are the examples supposed to work for this release? Because the instructions don't tell people how to get them running. I don't see the config.sh file. (I mentioned this in a previous email. I'll log a Jira.) William - Original Message - > I've put up an RC3 here: > > http://people.apache.org/~rhs/qpid-proton-0.1rc3/ > > The following are the changes from RC2: > > - added README and LICENSE for proton-j > - updated the proton-c README > - fixed cmake build to not use the OPTIONAL thing for > older > versions > - fixed detection of LIB_SUFFIX (i.e. we won't install > into > lib64 > on 32 > bit systems anymore) > > --Rafael >>
Re: RC3
Centos5 x64 build failure - funny didn't I see this before? [ 69%] Building C object CMakeFiles/qpid-proton.dir/src/driver.c.o /home/kgiusti/proton/qpid-proton-c-0.1/src/driver.c:75:1: error: "NAME_MAX" redefined In file included from /usr/include/bits/local_lim.h:36, from /usr/include/bits/posix1_lim.h:153, from /usr/include/limits.h:145, from /usr/lib/gcc/x86_64-redhat-linux/4.1.2/include/limits.h:122, from /usr/lib/gcc/x86_64-redhat-linux/4.1.2/include/syslimits.h:7, from /usr/lib/gcc/x86_64-redhat-linux/4.1.2/include/limits.h:11, from /usr/include/bits/socket.h:31, from /usr/include/sys/socket.h:35, from /home/kgiusti/proton/qpid-proton-c-0.1/src/driver.c:29: /usr/include/linux/limits.h:13:1: error: this is the location of the previous definition make[2]: *** [CMakeFiles/qpid-proton.dir/src/driver.c.o] Error 1 make[1]: *** [CMakeFiles/qpid-proton.dir/all] Error 2 make: *** [all] Error 2 -K - Original Message - > Are the examples supposed to work for this release? Because the > instructions don't tell people how to get them running. I don't see > the config.sh file. (I mentioned this in a previous email. I'll log > a Jira.) > > William > > - Original Message - > > I've put up an RC3 here: > > > > http://people.apache.org/~rhs/qpid-proton-0.1rc3/ > > > > The following are the changes from RC2: > > > > - added README and LICENSE for proton-j > > - updated the proton-c README > > - fixed cmake build to not use the OPTIONAL thing for older > > versions > > - fixed detection of LIB_SUFFIX (i.e. we won't install into lib64 > > on 32 > > bit systems anymore) > > > > --Rafael > > >
Re: initial release candidate
The following patch fixes the problem with older versions of the SSL library.
It also works on the latest Fedora 17, so I think it's low risk.
Shall I commit it?
8<
diff --git a/proton-c/src/ssl/openssl.c b/proton-c/src/ssl/openssl.c
index 6ea951f..dd775cd 100644
--- a/proton-c/src/ssl/openssl.c
+++ b/proton-c/src/ssl/openssl.c
@@ -296,6 +296,14 @@ int pn_ssl_set_credentials( pn_ssl_t *ssl,
ssl->has_certificate = true;
+ // bug in older versions of OpenSSL: servers may request client cert even if
anonymous
+ // cipher was negotiated. TLSv1 will reject such a request. Hack: once a
cert is
+ // configured, allow only authenticated ciphers.
+ if (!SSL_CTX_set_cipher_list( ssl->ctx, CIPHERS_AUTHENTICATE )) {
+ _log_ssl_error(ssl, "Failed to set cipher list to %s\n",
CIPHERS_AUTHENTICATE);
+ return -6;
+ }
+
_log( ssl, "Configured local certificate file %s\n", certificate_file );
return 0;
}
@@ -543,6 +551,7 @@ pn_ssl_t *pn_ssl(pn_transport_t *transport)
ssl_initialized = 1;
SSL_library_init();
SSL_load_error_strings();
+OpenSSL_add_all_algorithms();
}
pn_ssl_t *ssl = calloc(1, sizeof(pn_ssl_t));
>8
- Original Message -
> Interesting - that test uses a certificate I created and checked into
> the repo. I generated the certificate using a newer toolset.
>
> I'll have a look at it...
>
>
> -K
>
> - Original Message -
> > My (64-bit) Ubuntu 12.04 works fine...
> >
> > On Ubuntu 10.04 I'm seeing SSL errors... presumably these are
> > related
> > to the age of the ssl library and the algorithms it supports...
> >
> > proton_tests.ssl.SslTest.test_client_authentication
> > .SSL_CTX_use_PrivateKey_file(
> > /home/rob/qpid-proton-c-0.1/tests/proton_tests/ssl_db/server-private-key.pem
> > ) failed
> > error:06074079:digital envelope routines:EVP_PBE_CipherInit:unknown
> > pbe algorithm
> > error:23077073:PKCS12 routines:PKCS12_pbe_crypt:pkcs12 algor
> > cipherinit error
> > error:2306A075:PKCS12 routines:PKCS12_item_decrypt_d2i:pkcs12 pbe
> > crypt error
> > error:0907B00D:PEM routines:PEM_READ_BIO_PRIVATEKEY:ASN1 lib
> > error:140B0009:SSL routines:SSL_CTX_use_PrivateKey_file:PEM lib
> > fail
> > Error during test: Traceback (most recent call last):
> > File "./proton-test", line 331, in run
> > phase()
> > File "/home/rob/qpid-proton-c-0.1/tests/proton_tests/ssl.py",
> > line
> > 130, in test_client_authentication
> > "server-password")
> > File "/home/rob/qpid-proton-c-0.1/bindings/python/proton.py",
> > line
> > 2111, in set_credentials
> > password) )
> > File "/home/rob/qpid-proton-c-0.1/bindings/python/proton.py",
> > line
> > 2096, in _check
> > raise exc("SSL failure.")
> > SSLException: SSL failure.
> >
> > -- Rob
> >
> > On 24 October 2012 18:05, Ken Giusti wrote:
> > > Ubuntu 12.04-1 LTS, fully patched and up to date:
> > >
> > > 1) had to install the following packages - similar to the README,
> > > but ubuntu specific:
> > >
> > > sudo apt-get install cmake swig libssl-dev python-dev ruby
> > > ruby-dev
> > > python-epydoc uuid-dev
> > >
> > > [note: cmake is version 2.8.7, so I didn't get that OPTIONAL
> > > issue]
> > >
> > > 2) make and install went well!
> > >
> > > 3) example/send.py and recv.py worked - need to try with SSL
> > > next..
> > >
> > > 4) am seeing a failure in the python-tests:
> > >
> > > proton_tests.codec.DataTest.testDecimal128
> > >
> > > pass
> > > proton_tests.codec.DataTest.testDecimal32
> > > .
> > > pass
> > > proton_tests.codec.DataTest.testDecimal64
> > > .
> > > fail
> > > Error during test: Traceback (most recent call last):
> > > File "./proton-test", line 331, in run
> > > phase()
> > > File
> > >
> > > "/home/kgiusti/proton-rc/qpid-proton-c-0.1/tests/proton_tests/codec.py",
> > > line 246, in testDecimal64
> > > self._test("decimal64", 0, 1, 2, 3, 4, 2**60)
> > > File
> > >
> > > "/home/kgiusti/proton-rc/qpid-proton-c-0.1/tests/proton_tests/codec.py",
> > > line 183, in _test
> > > putter(v)
> > > File
> > >
> > > "/home/kgiusti/proton-rc/install/lib/python2.7/dist-packages/proton.py",
> > > line 1134, in put_decimal64
> > > self._check(pn_data_put_decimal64(self._data, d))
> > > TypeError: in method 'pn_data_put_decimal64', argument 2 of
> > > type
> > > 'pn_decimal64_t'
> > > proton_tests.codec.DataTest.testDescribedEmptyArray
> > >
Re: RC3
Done. I stopped short of putting "Hey William! Set the install prefix." ;-) --Rafael On Wed, Oct 24, 2012 at 11:22 PM, William Henry wrote: > Change: > # depending on your system you may want to adjust the install prefix > cmake -DCMAKE_INSTALL_PREFIX=/usr .. > > To: > # Set the install prefix. You may need to adjust depending on your system > cmake -DCMAKE_INSTALL_PREFIX=/usr .. > > > - Original Message - > > It looks like you installed everything into /usr/local. I'm guessing > > the > > system python (installed in /usr) does not look under /usr/local as > > part of > > it's module search path. Try installing into /usr instead. > > > > --Rafael > > > > On Wed, Oct 24, 2012 at 10:10 PM, William Henry > > wrote: > > > > > $ more build/install_manifest.txt > > > /usr/local/bin/proton > > > /usr/local/bin/proton-dump > > > /usr/local/lib64/libqpid-proton.so > > > /usr/local/include/proton/parser.h > > > /usr/local/include/proton/util.h > > > /usr/local/include/proton/ssl.h > > > /usr/local/include/proton/scanner.h > > > /usr/local/include/proton/cproton.i > > > /usr/local/include/proton/messenger.h > > > /usr/local/include/proton/message.h > > > /usr/local/include/proton/sasl.h > > > /usr/local/include/proton/driver.h > > > /usr/local/include/proton/types.h > > > /usr/local/include/proton/buffer.h > > > /usr/local/include/proton/framing.h > > > /usr/local/include/proton/codec.h > > > /usr/local/include/proton/engine.h > > > /usr/local/include/proton/error.h > > > /usr/local/share/proton/LICENSE > > > /usr/local/share/proton/README > > > /usr/local/share/proton/TODO > > > /usr/local/lib64/pkgconfig/libqpid-proton.pc > > > /usr/local/lib64/python2.7/site-packages/cproton.py > > > /usr/local/lib64/python2.7/site-packages/cproton.pyc > > > /usr/local/lib64/python2.7/site-packages/cproton.pyo > > > /usr/local/lib64/python2.7/site-packages/proton.py > > > /usr/local/lib64/python2.7/site-packages/proton.pyc > > > /usr/local/lib64/python2.7/site-packages/proton.pyo > > > /usr/local/lib64/python2.7/site-packages/_cproton.so > > > /usr/local/lib64/ruby/cproton.so > > > /usr/local/lib64/php/modules/cproton.so > > > /usr/local/share/php/cproton.php > > > /usr/local/share/php/proton.php > > > /etc/php.d/cproton.ini > > > > > > > > > - Original Message - > > > > Can you post the contents of your install_manifest.txt? > > > > > > > > On Wed, Oct 24, 2012 at 9:50 PM, William Henry > > > > > > > > wrote: > > > > > > > > > Ok install was successful. Still have an ImportError for > > > > > proton. > > > > > > > > > > Not sure what I'm missing > > > > > > > > > > William > > > > > > > > > > Sent from my iPhone > > > > > > > > > > On Oct 24, 2012, at 7:29 PM, Rafael Schloming > > > > > > > > > > wrote: > > > > > > > > > > > The examples should work without the config.sh, it just sets > > > > > > up > > > > > > stuff for > > > > > > the dev environment. If you do the make install, all the > > > > > > proton > > > > > > stuff > > > > > > should be available without any special environmental config. > > > > > > > > > > > > --Rafael > > > > > > > > > > > > On Wed, Oct 24, 2012 at 8:11 PM, William Henry > > > > > > > > > > > wrote: > > > > > > > > > > > >> Are the examples supposed to work for this release? Because > > > > > >> the > > > > > >> instructions don't tell people how to get them running. I > > > > > >> don't > > > > > >> see the > > > > > >> config.sh file. (I mentioned this in a previous email. I'll > > > > > >> log > > > > > >> a Jira.) > > > > > >> > > > > > >> William > > > > > >> > > > > > >> - Original Message - > > > > > >>> I've put up an RC3 here: > > > > > >>> > > > > > >>> http://people.apache.org/~rhs/qpid-proton-0.1rc3/ > > > > > >>> > > > > > >>> The following are the changes from RC2: > > > > > >>> > > > > > >>> - added README and LICENSE for proton-j > > > > > >>> - updated the proton-c README > > > > > >>> - fixed cmake build to not use the OPTIONAL thing for > > > > > >>> older > > > > > >>> versions > > > > > >>> - fixed detection of LIB_SUFFIX (i.e. we won't install > > > > > >>> into > > > > > >>> lib64 > > > > > >>> on 32 > > > > > >>> bit systems anymore) > > > > > >>> > > > > > >>> --Rafael > > > > > >> > > > > > > > > > > > > > > >
