Re: RC2
There's a blocker bug in proton-c RC2. I'm investigating... It appears that messenger truncates the address in the to field on sent messages so that it only contains the scheme://host portion. -Ted On 10/24/2012 08:19 AM, Rafael Schloming wrote: I've uploaded another release candidate here: http://people.apache.org/~rhs/qpid-proton-0.1rc2/ The following fixes were made: 1. the install step should now work without the documentation 2. the README has a note about root privileges 3. the tarball names/directory match 4. added some missing type mappings to the python binding 5. added the maven magic to update the pom version 6. I believe rob fixed PROTON-85 for the java code --Rafael
Re: RC2
I'm looking into why this isn't being auto detected properly. You can always override LIB_SUFFIX manually, i.e. add -DLIB_SUFFIX= to the command line. (I thought rpm was supposed to do this for you, but maybe not.) --Rafael On Wed, Oct 24, 2012 at 9:00 AM, Darryl L. Pierce dpie...@redhat.comwrote: On Wed, Oct 24, 2012 at 08:19:34AM -0400, Rafael Schloming wrote: I've uploaded another release candidate here: http://people.apache.org/~rhs/qpid-proton-0.1rc2/ The following fixes were made: 1. the install step should now work without the documentation 2. the README has a note about root privileges 3. the tarball names/directory match 4. added some missing type mappings to the python binding 5. added the maven magic to update the pom version 6. I believe rob fixed PROTON-85 for the java code I'm hitting a very strange error while doing a koji build for i686. For some reason the build environment is installing the file to /usr/lib64 rather than /usr/lib on 32-bit. http://koji.fedoraproject.org/koji/taskinfo?taskID=4621731 -- 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: RC2
cmake version 2.6-patch 4 -K - Original Message - I think this may be related to the cmake version. Can you guys run cmake -version and tell me what it reports? On Wed, Oct 24, 2012 at 10:17 AM, Rob Godfrey rob.j.godf...@gmail.comwrote: I get the same error on CentOS 6.3: [rob@seelachs build]$ cmake -DCMAKE_INSTALL_PREFIX=/usr .. -- The C compiler identification is GNU -- Check for working C compiler: /usr/bin/gcc -- Check for working C compiler: /usr/bin/gcc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Found OpenSSL: /usr/lib/libssl.so -- Found PythonLibs: /usr/lib/python2.6/config/libpython2.6.so -- Found PythonInterp: /usr/bin/python2.6 CMake Error at bindings/python/CMakeLists.txt:29 (install): install DIRECTORY given unknown argument OPTIONAL. -- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE) -- Configuring incomplete, errors occurred! [rob@seelachs build]$ more /etc/redhat-release CentOS release 6.3 (Final) On 24 October 2012 16:05, Ken Giusti kgiu...@redhat.com wrote: cmake fails on clean Centos5 machine: [kgiusti@centos5 build]$ cmake -DCMAKE_INSTALL_PREFIX=/home/kgiusti/proton/insta ll .. -- The C compiler identification is GNU -- Check for working C compiler: /usr/bin/gcc -- Check for working C compiler: /usr/bin/gcc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Found OpenSSL: /usr/lib64/libssl.so -- Found PythonLibs: /usr/lib64/python2.4/config/libpython2.4.a -- Found PythonInterp: /usr/bin/python2.4 -- Found Doxygen: /usr/bin/doxygen CMake Error at docs/api/CMakeLists.txt:28 (install): install DIRECTORY given unknown argument OPTIONAL. -- Configuring incomplete, errors occurred! [kgiusti@centos5 build]$ -K - Original Message - I've uploaded another release candidate here: http://people.apache.org/~rhs/qpid-proton-0.1rc2/ The following fixes were made: 1. the install step should now work without the documentation 2. the README has a note about root privileges 3. the tarball names/directory match 4. added some missing type mappings to the python binding 5. added the maven magic to update the pom version 6. I believe rob fixed PROTON-85 for the java code --Rafael
Re: RC2
As an aside, I have built successfully on Ubuntu 10.10 and 12.04. -- Rob On 24 October 2012 16:49, Rob Godfrey rob.j.godf...@gmail.com wrote: [rob@seelachs ~]$ cmake -version cmake version 2.6-patch 4 On 24 October 2012 16:39, Ken Giusti kgiu...@redhat.com wrote: cmake version 2.6-patch 4 -K - Original Message - I think this may be related to the cmake version. Can you guys run cmake -version and tell me what it reports? On Wed, Oct 24, 2012 at 10:17 AM, Rob Godfrey rob.j.godf...@gmail.comwrote: I get the same error on CentOS 6.3: [rob@seelachs build]$ cmake -DCMAKE_INSTALL_PREFIX=/usr .. -- The C compiler identification is GNU -- Check for working C compiler: /usr/bin/gcc -- Check for working C compiler: /usr/bin/gcc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Found OpenSSL: /usr/lib/libssl.so -- Found PythonLibs: /usr/lib/python2.6/config/libpython2.6.so -- Found PythonInterp: /usr/bin/python2.6 CMake Error at bindings/python/CMakeLists.txt:29 (install): install DIRECTORY given unknown argument OPTIONAL. -- Could NOT find Doxygen (missing: DOXYGEN_EXECUTABLE) -- Configuring incomplete, errors occurred! [rob@seelachs build]$ more /etc/redhat-release CentOS release 6.3 (Final) On 24 October 2012 16:05, Ken Giusti kgiu...@redhat.com wrote: cmake fails on clean Centos5 machine: [kgiusti@centos5 build]$ cmake -DCMAKE_INSTALL_PREFIX=/home/kgiusti/proton/insta ll .. -- The C compiler identification is GNU -- Check for working C compiler: /usr/bin/gcc -- Check for working C compiler: /usr/bin/gcc -- works -- Detecting C compiler ABI info -- Detecting C compiler ABI info - done -- Found OpenSSL: /usr/lib64/libssl.so -- Found PythonLibs: /usr/lib64/python2.4/config/libpython2.4.a -- Found PythonInterp: /usr/bin/python2.4 -- Found Doxygen: /usr/bin/doxygen CMake Error at docs/api/CMakeLists.txt:28 (install): install DIRECTORY given unknown argument OPTIONAL. -- Configuring incomplete, errors occurred! [kgiusti@centos5 build]$ -K - Original Message - I've uploaded another release candidate here: http://people.apache.org/~rhs/qpid-proton-0.1rc2/ The following fixes were made: 1. the install step should now work without the documentation 2. the README has a note about root privileges 3. the tarball names/directory match 4. added some missing type mappings to the python binding 5. added the maven magic to update the pom version 6. I believe rob fixed PROTON-85 for the java code --Rafael
Re: RC2
On Wed, 2012-10-24 at 10:32 -0400, Rafael Schloming wrote: I think this may be related to the cmake version. Can you guys run cmake -version and tell me what it reports? I think it's more likely missing quotes around a variable expansion that in this case expands to nothing. Andrew
Re: RC2
On Wed, 2012-10-24 at 11:27 -0400, Rafael Schloming wrote:
According to the cmake docs for 2.6.x, the install (DIRECTORY ...) command
doesn't have the OPTIONAL argument. Any ideas on how to work around this?
Why not force the doc build? That's what I did with the qpid cmake build
- it's really nasty because it builds unconditionally every time, but
it'll always be there when you try to install. If you find a better
approach let me know and I'll use it qpid too!
Another possibility might be to make the doc build part of the install
phase instead with something like:
install (CODE execute_process(COMMAND ${DOXYGEN_EXECUTABLE}
user.doxygen))
However then either you don't get make docs to work or you get it
built twice if you do build the docs.
Andrew
Re: RC2
I'm a little stumped by this one. I'm thinking the compiler settings must be quite different from how we normally build, but I'm not sure why. --Rafael On Wed, Oct 24, 2012 at 11:03 AM, Darryl L. Pierce dpie...@redhat.comwrote: On Wed, Oct 24, 2012 at 10:36:11AM -0400, Rafael Schloming wrote: I'm looking into why this isn't being auto detected properly. You can always override LIB_SUFFIX manually, i.e. add -DLIB_SUFFIX= to the command line. (I thought rpm was supposed to do this for you, but maybe not.) No, it does. My bad for not using the %cmake macros. Now, though, the package fails to build [1] due to compiler warnings treated as errors. [1] http://koji.fedoraproject.org/koji/taskinfo?taskID=4622418 -- 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: RC2
On Wed, 2012-10-24 at 13:44 -0400, Rafael Schloming wrote: On Wed, Oct 24, 2012 at 12:54 PM, Andrew Stitcher astitc...@redhat.comwrote: ... How do you force the doc build? As below. I couldn't figure out how to add dependencies between built-in and custom targets. There is no way to do this - it's a long standing feature request for cmake. Is there any way to just force the doc build for old versions? add ALL after the target name, viz: add_custom_target (docs-c ALL ... Andrew
