You are viewing a plain text version of this content. The canonical link for it is here.
Posted to proton@qpid.apache.org by Rafael Schloming <rh...@alum.mit.edu> on 2012/10/24 21:29:44 UTC
RC3
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
Posted by "Darryl L. Pierce" <dp...@redhat.com>.
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/
RE: RC3
Posted by Mary Hinton <m....@nc.rr.com>.
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:rhs@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 <m....@nc.rr.com> 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 <unistd.h>
> #include <stdbool.h>
>
> -----Original Message-----
> From: Rafael Schloming [mailto:rhs@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
> <dp...@redhat.com>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 <proton/message.h>
> > #include <proton/util.h>
> > #include <unistd.h>
> > +#include <libgen.h>
> > #include "util.h"
> > #include "pn_config.h"
> > #include <proton/codec.h>
> > @@ -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
> > <address>] [-m <sasl-mech>]\n", argv[0]);
> > + printf("Usage: %s [-h] [-c [user[:password]@]host[:port]] [-a
> > <address>] [-m <sasl-mech>]\n", basename(argv[0]));
> > printf("\n");
> > printf(" -c The connect url.\n");
> > printf(" -a The 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
Posted by Rafael Schloming <rh...@alum.mit.edu>.
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 <m....@nc.rr.com> 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 <unistd.h>
> #include <stdbool.h>
>
> -----Original Message-----
> From: Rafael Schloming [mailto:rhs@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
> <dp...@redhat.com>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 <proton/message.h>
> > #include <proton/util.h>
> > #include <unistd.h>
> > +#include <libgen.h>
> > #include "util.h"
> > #include "pn_config.h"
> > #include <proton/codec.h>
> > @@ -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
> > <address>] [-m <sasl-mech>]\n", argv[0]);
> > + printf("Usage: %s [-h] [-c [user[:password]@]host[:port]] [-a
> > <address>] [-m <sasl-mech>]\n", basename(argv[0]));
> > printf("\n");
> > printf(" -c The connect url.\n");
> > printf(" -a The 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
Posted by Mary Hinton <m....@nc.rr.com>.
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 <unistd.h>
#include <stdbool.h>
-----Original Message-----
From: Rafael Schloming [mailto:rhs@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
<dp...@redhat.com>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 <proton/message.h>
> #include <proton/util.h>
> #include <unistd.h>
> +#include <libgen.h>
> #include "util.h"
> #include "pn_config.h"
> #include <proton/codec.h>
> @@ -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
> <address>] [-m <sasl-mech>]\n", argv[0]);
> + printf("Usage: %s [-h] [-c [user[:password]@]host[:port]] [-a
> <address>] [-m <sasl-mech>]\n", basename(argv[0]));
> printf("\n");
> printf(" -c The connect url.\n");
> printf(" -a The 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
Posted by Rafael Schloming <rh...@alum.mit.edu>.
What's libgen.h? Is that available on windows?
--Rafael
On Thu, Oct 25, 2012 at 10:38 AM, Darryl L. Pierce <dp...@redhat.com>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 <proton/message.h>
> #include <proton/util.h>
> #include <unistd.h>
> +#include <libgen.h>
> #include "util.h"
> #include "pn_config.h"
> #include <proton/codec.h>
> @@ -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
> <address>] [-m <sasl-mech>]\n", argv[0]);
> + printf("Usage: %s [-h] [-c [user[:password]@]host[:port]] [-a
> <address>] [-m <sasl-mech>]\n", basename(argv[0]));
> printf("\n");
> printf(" -c The connect url.\n");
> printf(" -a The 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
Posted by "Darryl L. Pierce" <dp...@redhat.com>.
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 <proton/message.h>
#include <proton/util.h>
#include <unistd.h>
+#include <libgen.h>
#include "util.h"
#include "pn_config.h"
#include <proton/codec.h>
@@ -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
<address>] [-m <sasl-mech>]\n", argv[0]);
+ printf("Usage: %s [-h] [-c [user[:password]@]host[:port]] [-a
<address>] [-m <sasl-mech>]\n", basename(argv[0]));
printf("\n");
printf(" -c The connect url.\n");
printf(" -a The 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
Posted by "Darryl L. Pierce" <dp...@redhat.com>.
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/
Re: RC3
Posted by Rafael Schloming <rh...@alum.mit.edu>.
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 <dp...@redhat.com>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
Posted by "Darryl L. Pierce" <dp...@redhat.com>.
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
Posted by Rob Godfrey <ro...@gmail.com>.
I got the following failure on proton-c from this release on 32-bit
Ubuntu 12.04:
proton_tests.codec.DataTest.testDecimal64
............................................................................................................
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/codec.py",
line 246, in testDecimal64
self._test("decimal64", 0, 1, 2, 3, 4, 2**60)
File "/home/rob/qpid-proton-c-0.1/tests/proton_tests/codec.py",
line 183, in _test
putter(v)
File "/home/rob/qpid-proton-c-0.1/bindings/python/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'
On 24 October 2012 21:29, Rafael Schloming <rh...@alum.mit.edu> 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)
>
> --Rafael
Re: RC3
Posted by William Henry <wh...@redhat.com>.
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 <rh...@alum.mit.edu> 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 <wh...@redhat.com> 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 <wh...@redhat.com>
>>> 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
>>>>> <wh...@redhat.com>
>>>>> 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
>>>>>> <rh...@alum.mit.edu>
>>>>>> 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
>>>>>>> <wh...@redhat.com>
>>>>>> 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
Posted by Rafael Schloming <rh...@alum.mit.edu>.
Done. I stopped short of putting "Hey William! Set the install prefix." ;-)
--Rafael
On Wed, Oct 24, 2012 at 11:22 PM, William Henry <wh...@redhat.com> 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 <wh...@redhat.com>
> > 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
> > > > <wh...@redhat.com>
> > > > 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
> > > > > <rh...@alum.mit.edu>
> > > > > 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
> > > > > > <wh...@redhat.com>
> > > > > 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
Posted by William Henry <wh...@redhat.com>.
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 <wh...@redhat.com>
> 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
> > > <wh...@redhat.com>
> > > 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
> > > > <rh...@alum.mit.edu>
> > > > 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
> > > > > <wh...@redhat.com>
> > > > 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
Posted by Rafael Schloming <rh...@alum.mit.edu>.
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 <wh...@redhat.com> 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 <wh...@redhat.com>
> > 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 <rh...@alum.mit.edu>
> > > 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
> > > > <wh...@redhat.com>
> > > 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
Posted by William Henry <wh...@redhat.com>.
$ 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 <wh...@redhat.com>
> 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 <rh...@alum.mit.edu>
> > 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
> > > <wh...@redhat.com>
> > 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
Posted by Rafael Schloming <rh...@alum.mit.edu>.
Can you post the contents of your install_manifest.txt?
On Wed, Oct 24, 2012 at 9:50 PM, William Henry <wh...@redhat.com> 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 <rh...@alum.mit.edu> 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 <wh...@redhat.com>
> 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
Posted by William Henry <wh...@redhat.com>.
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 <rh...@alum.mit.edu> 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 <wh...@redhat.com> 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
Posted by William Henry <wh...@redhat.com>.
Thanks I'll try that. Sorry I guess I had built up a habit.
Sent from my iPhone
On Oct 24, 2012, at 7:29 PM, Rafael Schloming <rh...@alum.mit.edu> 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 <wh...@redhat.com> 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
Posted by Rafael Schloming <rh...@alum.mit.edu>.
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 <wh...@redhat.com> 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
Posted by Rafael Schloming <rh...@alum.mit.edu>.
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 <kg...@redhat.com> 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: RC3
Posted by Ken Giusti <kg...@redhat.com>.
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
Posted by Ken Giusti <kg...@redhat.com>.
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
Posted by William Henry <wh...@redhat.com>.
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
>