Ted,

The following is the output with warning as errors suppressed.

Paul

<path>/shop/qpid-dispatch-0.5/src/lrp.c: In function ‘qd_lrpc_open_handler’:
<path>/shop/qpid-dispatch-0.5/src/lrp.c:59: warning: dereferencing type-punned 
pointer will break strict-aliasing rules
<path>/shop/qpid-dispatch-0.5/src/lrp.c: In function ‘qd_lrpc_close_handler’:
<path>/shop/qpid-dispatch-0.5/src/lrp.c:115: warning: dereferencing type-punned 
pointer will break strict-aliasing rules
<path>/shop/qpid-dispatch-0.5/src/python_embedded.c: In function 
‘qd_py_to_composed’:
<path>/shop/qpid-dispatch-0.5/src/python_embedded.c:152: error: ‘Py_ssize_t’ 
undeclared (first use in this function)
<path>/shop/qpid-dispatch-0.5/src/python_embedded.c:152: error: (Each 
undeclared identifier is reported only once
<path>/shop/qpid-dispatch-0.5/src/python_embedded.c:152: error: for each 
function it appears in.)
<path>/shop/qpid-dispatch-0.5/src/python_embedded.c:152: error: expected ‘;’ 
before ‘iter’
<path>/shop/qpid-dispatch-0.5/src/python_embedded.c:156: error: ‘iter’ 
undeclared (first use in this function)
<path>/shop/qpid-dispatch-0.5/src/python_embedded.c:165: error: expected ‘;’ 
before ‘count’
<path>/shop/qpid-dispatch-0.5/src/python_embedded.c:166: error: ‘count’ 
undeclared (first use in this function)
<path>/shop/qpid-dispatch-0.5/src/python_embedded.c:170: error: expected ‘;’ 
before ‘idx’
<path>/shop/qpid-dispatch-0.5/src/python_embedded.c:170: error: ‘idx’ 
undeclared (first use in this function)
<path>/shop/qpid-dispatch-0.5/src/python_embedded.c:179: error: expected ‘;’ 
before ‘count’
<path>/shop/qpid-dispatch-0.5/src/python_embedded.c:184: error: expected ‘;’ 
before ‘idx’
<path>/shop/qpid-dispatch-0.5/src/python_embedded.c: In function 
‘qd_py_attr_to_composed’:
<path>/shop/qpid-dispatch-0.5/src/python_embedded.c:211: warning: passing 
argument 2 of ‘PyObject_GetAttrString’ discards qualifiers from pointer target 
type
<path>/shop/qpid-dispatch-0.5/src/python_embedded.c: At top level:
<path>/shop/qpid-dispatch-0.5/src/python_embedded.c:428: warning: excess 
elements in struct initializer
<path>/shop/qpid-dispatch-0.5/src/python_embedded.c:428: warning: (near 
initialization for ‘LogAdapterType’)
<path>/shop/qpid-dispatch-0.5/src/python_embedded.c: In function 
‘iter_to_py_attr’:
<path>/shop/qpid-dispatch-0.5/src/python_embedded.c:481: warning: passing 
argument 2 of ‘PyObject_SetAttrString’ discards qualifiers from pointer target 
type
<path>/shop/qpid-dispatch-0.5/src/python_embedded.c: At top level:
<path>/shop/qpid-dispatch-0.5/src/python_embedded.c:675: warning: excess 
elements in struct initializer
<path>/shop/qpid-dispatch-0.5/src/python_embedded.c:675: warning: (near 
initialization for ‘IoAdapterType’)
<path>/shop/qpid-dispatch-0.5/src/python_embedded.c: In function 
‘qd_register_constant’:
<path>/shop/qpid-dispatch-0.5/src/python_embedded.c:686: warning: passing 
argument 2 of ‘PyModule_AddObject’ discards qualifiers from pointer target type
make[2]: *** [src/CMakeFiles/qpid-dispatch.dir/python_embedded.c.o] Error 1
<path>/shop/qpid-dispatch-0.5/src/router_config.c: In function 
‘qd_router_configure_lrp’:
<path>/shop/qpid-dispatch-0.5/src/router_config.c:220: warning: dereferencing 
type-punned pointer will break strict-aliasing rules
<path>/shop/qpid-dispatch-0.5/src/router_node.c: In function 
‘router_outgoing_link_handler’:
<path>/shop/qpid-dispatch-0.5/src/router_node.c:1392: warning: dereferencing 
type-punned pointer will break strict-aliasing rules
<path>/shop/qpid-dispatch-0.5/src/router_node.c: In function 
‘qd_router_register_address’:
<path>/shop/qpid-dispatch-0.5/src/router_node.c:1938: warning: dereferencing 
type-punned pointer will break strict-aliasing rules
<path>/shop/qpid-dispatch-0.5/src/router_pynode.c: In function 
‘qd_set_valid_origins’:
<path>/shop/qpid-dispatch-0.5/src/router_pynode.c:371: error: ‘Py_ssize_t’ 
undeclared (first use in this function)
<path>/shop/qpid-dispatch-0.5/src/router_pynode.c:371: error: (Each undeclared 
identifier is reported only once
<path>/shop/qpid-dispatch-0.5/src/router_pynode.c:371: error: for each function 
it appears in.)
<path>/shop/qpid-dispatch-0.5/src/router_pynode.c:371: error: expected ‘;’ 
before ‘idx’
<path>/shop/qpid-dispatch-0.5/src/router_pynode.c:395: error: expected ‘;’ 
before ‘origin_count’
<path>/shop/qpid-dispatch-0.5/src/router_pynode.c:399: error: ‘idx’ undeclared 
(first use in this function)
<path>/shop/qpid-dispatch-0.5/src/router_pynode.c:399: error: ‘origin_count’ 
undeclared (first use in this function)
<path>/shop/qpid-dispatch-0.5/src/router_pynode.c: At top level:
<path>/shop/qpid-dispatch-0.5/src/router_pynode.c:610: warning: excess elements 
in struct initializer
<path>/shop/qpid-dispatch-0.5/src/router_pynode.c:610: warning: (near 
initialization for ‘RouterAdapterType’)
make[2]: *** [src/CMakeFiles/qpid-dispatch.dir/router_pynode.c.o] Error 1
make[2]: Target `src/CMakeFiles/qpid-dispatch.dir/build' not remade because of 
errors.
make[1]: *** [src/CMakeFiles/qpid-dispatch.dir/all] Error 2
make[1]: Target `all' not remade because of errors.
make: *** [all] Error 2
make: Target `default_target' not remade because of errors.


________________________________________
From: Ted Ross [[email protected]]
Sent: Thursday, February 11, 2016 9:50 AM
To: [email protected]
Subject: Re: Help with Dispatch Build "difficulties"

Paul,

Can you run a "make -k" on your Dispatch source to get a more complete
list of build failures?  I'd like to have a look at them.

If you have proton 0.11, then dispatch _should_ build.

-Ted

On 02/11/2016 10:14 AM, Flores, Paul A. wrote:
> Hi Ganesh,
>
> I have proton 0.11 compiled and examples working.  I am using gcc version 
> 4.1.2 and I have Python 2.6.8 installed.
>
> While moving to Centos 7 is in the works is there any other way to get past 
> this issue?
>
> There is considerable interest in demonstrating dispatch prior to a "deeper" 
> commitment.
>
> Thanks.
> ________________________________________
> From: Ganesh Murthy [[email protected]]
> Sent: Thursday, February 11, 2016 8:36 AM
> To: [email protected]
> Subject: Re: Hekp with Dispatch Build "difficulties"
>
> Hi Paul,
>      I tried to get a Docker environment going with CentOS 5 but ran into 
> several problems. CentOS 5 is pre-2008 and has an old version of Python. Is 
> there a way you can get to a recent version of CentOS (CentOS 7?). If you 
> want to stay on CentOS 5, please try using dispatch 0.4 and proton 0.9.
>
> Thanks.
>
> ----- Original Message -----
> From: "Paul A. Flores" <[email protected]>
> To: [email protected]
> Sent: Wednesday, February 10, 2016 5:40:18 PM
> Subject: Hekp with Dispatch Build "difficulties"
>
> I have been trying to get Dispatch 0.5 to build.
>
>
>
> I am seeing the following issue.  Can anyone help me get past this issue?
>
>
>
> [ 26%] Building C object src/CMakeFiles/qpid-dispatch.dir/lrp.c.o
> cc1: warnings being treated as errors
> /home/pflores/shop/qpid-dispatch-0.5/src/lrp.c: In function 
> ‘qd_lrpc_open_handler’:
> /home/pflores/shop/qpid-dispatch-0.5/src/lrp.c:59: warning: dereferencing 
> type-punned pointer will break strict-aliasing rules
> /home/pflores/shop/qpid-dispatch-0.5/src/lrp.c: In function 
> ‘qd_lrpc_close_handler’:
> /home/pflores/shop/qpid-dispatch-0.5/src/lrp.c:115: warning: dereferencing 
> type-punned pointer will break strict-aliasing rules
> make[2]: *** [src/CMakeFiles/qpid-dispatch.dir/lrp.c.o] Error 1
> make[1]: *** [src/CMakeFiles/qpid-dispatch.dir/all] Error 2
> make: *** [all] Error 2
>
> System is Centos 5.11
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to