Bug 812188
Summary: | FindPkgConfig.cmake not setting PKG_CONFIG_FOUND | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Rich Mattes <richmattes> |
Component: | cmake | Assignee: | Orion Poplawski <orion> |
Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | rawhide | CC: | jreznik, orion, pertusus, pmachata, rdieter |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
URL: | http://public.kitware.com/Bug/view.php?id=13125 | ||
Whiteboard: | |||
Fixed In Version: | cmake-2.8.8-0.4.rc2.fc18 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-04-14 22:09:45 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Rich Mattes
2012-04-13 02:33:17 UTC
Filed upstream. Building cmake-2.8.8-0.3.rc2.fc18 in rawhide now, which should fix this issue. Please test when available and note the result here. Seems still not fixed. I'm seeing failures building telepathy-qt4 too. put in some diagostic into the cmake module, find_package(PkgConfig) ... message(STATUS "PKG_CONFIG_FOUND, PkgConfig_FOUND : ${PKG_CONFIG_FOUND}, ${PkgConfig_FOUND}") and it prints: PKG_CONFIG_FOUND, PkgConfig_FOUND : , OK, found the problem from FindPackageHandleStandardArgs.cmake: # It also sets the <UPPERCASED_NAME>_FOUND variable. notice the *UPPERCASED* part, so set(PKG_CONFIG_FOUND "${PkgConfig_FOUND}") does not work, but set(PKG_CONFIG_FOUND "${PKGCONFIG_FOUND}") does. I'll adjust our local patch accordingly, and poke upstream. OK, I guess I'm silly today, can't figure out how to add a comment to the upstream report... Orion, mind helping me out there (or give me a clue how to do it)? Build cmake-2.8.8-0.4.rc2.fc18 , and confirmed good (for me) (In reply to comment #5) > OK, I guess I'm silly today, can't figure out how to add a comment to the > upstream report... Orion, mind helping me out there (or give me a clue how to > do it)? I think you need to reopen it first. Thanks for fixing this. I can't see any way for me to reopen it either, I guess I can just file a new one |