[ 
https://issues.apache.org/jira/browse/DISPATCH-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ganesh Murthy resolved DISPATCH-815.
------------------------------------
    Resolution: Fixed

Removed this one line from python/setup.py.in

{noformat}
scripts=['${CMAKE_SOURCE_DIR}/tools/qdstat', 
'${CMAKE_SOURCE_DIR}/tools/qdmanage'],
{noformat}

This solved the problem. 

> shebang python (#!/usr/bin/env python) gets evaluated on make install
> ---------------------------------------------------------------------
>
>                 Key: DISPATCH-815
>                 URL: https://issues.apache.org/jira/browse/DISPATCH-815
>             Project: Qpid Dispatch
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 0.8.0
>            Reporter: Ganesh Murthy
>            Assignee: Ganesh Murthy
>             Fix For: 1.0.0
>
>
> The first line on qdmanage and qdstat python scripts is the python shebang
> {noformat}
> #!/usr/bin/env python
> {noformat}
> When a make install is run from the dispatch build folder, the 
> <install_dir>/bin/qdstat and <install_dir>/bin/qdmanage python scripts have 
> their python shebang evaluated and the first line of the scripts look like 
> this - 
> {noformat}
> #!/usr/bin/python
> {noformat}
> This behavior is incorrect.
> Chris Richardson observed the following on the qpid users mailing list - 
> {noformat}
> It seems the problem here is not with CMake but actually with the
> qpid-dispatch code, which has duplicate install routines for the
> qdstat/qdmanager files. One is as Gordon described using
> install(PROGRAMS...) and the other is via the python distutils method using
> <qpid-dispatch>/python/setup.py.in; it is in fact distutils that munges the
> shebang as described and not CMake at all! Removing qdstat/qdmanager from
> setup.py.in fixes the problem.
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

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

Reply via email to