[ 
https://issues.apache.org/jira/browse/PROTON-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13750253#comment-13750253
 ] 

Darryl L. Pierce commented on PROTON-412:
-----------------------------------------

The way Fedora's packaging system, koji, invokes it is with:

/usr/bin/cmake -DCMAKE_C_FLAGS_RELEASE:STRING=-DNDEBUG 
-DCMAKE_CXX_FLAGS_RELEASE:STRING=-DNDEBUG 
-DCMAKE_Fortran_FLAGS_RELEASE:STRING=-DNDEBUG -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON 
-DCMAKE_INSTALL_PREFIX:PATH=/usr -DINCLUDE_INSTALL_DIR:PATH=/usr/include 
-DLIB_INSTALL_DIR:PATH=/usr/lib64 -DSYSCONF_INSTALL_DIR:PATH=/etc 
-DSHARE_INSTALL_PREFIX:PATH=/usr/share -DLIB_SUFFIX=64 
-DBUILD_SHARED_LIBS:BOOL=ON -DPROTON_DISABLE_RPATH=true .

                
> pkg-config has wrong configuration
> ----------------------------------
>
>                 Key: PROTON-412
>                 URL: https://issues.apache.org/jira/browse/PROTON-412
>             Project: Qpid Proton
>          Issue Type: Bug
>          Components: proton-c
>    Affects Versions: 0.4
>            Reporter: Darryl L. Pierce
>
> Description of problem:
> From /usr/lib64/pkgconfig/libqpid-proton.pc -
> prefix=/usr
> exec_prefix=/usr
> libdir=/usr/usr/lib64
> includedir=/usr/usr/include
> Note that prefix and exec_prefix are correct but libdir and includedir don't 
> make any sense.
> This might be an issue with the upstream package or the rpm packaging 
> process. It looks like there is an extraneous /usr/ in the way that libdir 
> and indlucedir are constructed.
> Version-Release number of selected component (if applicable):
> 0.4-3
> How reproducible:
> 100%
> Steps to Reproduce:
> 1. yum install qpid-proton-c-devel
> 2.
> 3.
> Actual results:
> As description
> Expected results:
> File extract above should be:
> prefix=/usr
> exec_prefix=/usr
> libdir=/usr/lib64
> includedir=/usr/include
> Additional info:

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to