Re: RC3

2012-10-25 Thread Ken Giusti
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

2012-10-25 Thread William Henry
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 r...@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 whe...@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 whe...@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
 whe...@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
 r...@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
 whe...@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

2012-10-24 Thread Rob Godfrey
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 r...@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

2012-10-24 Thread Darryl L. Pierce
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/



pgpjEV36bLpuC.pgp
Description: PGP signature


Re: RC3

2012-10-24 Thread Rafael Schloming
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 whe...@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

2012-10-24 Thread William Henry
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 r...@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 whe...@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

2012-10-24 Thread Rafael Schloming
Can you post the contents of your install_manifest.txt?

On Wed, Oct 24, 2012 at 9:50 PM, William Henry whe...@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 r...@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 whe...@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

2012-10-24 Thread William Henry
$ 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 whe...@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 r...@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
   whe...@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

2012-10-24 Thread Rafael Schloming
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 whe...@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 whe...@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 r...@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
whe...@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

2012-10-24 Thread William Henry
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 whe...@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
   whe...@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
r...@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
 whe...@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