Bug 876118
| Summary: | Inconsistent results of FindPythonInterp and FindPythonLibs | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Jaroslav Škarvada <jskarvad> | ||||
| Component: | cmake | Assignee: | Orion Poplawski <orion> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 19 | CC: | besser82, dpierce, jreznik, kdudka, kevin, ltinkl, orion, pertusus, pmachata, rdieter | ||||
| Target Milestone: | --- | Keywords: | Reopened | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | http://public.kitware.com/Bug/view.php?id=13794 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | cmake-2.8.12-2.fc19 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-10-31 02:58:27 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: | |||||||
| Attachments: |
|
||||||
|
Description
Jaroslav Škarvada
2012-11-13 11:23:22 UTC
Created attachment 644062 [details]
Simple config (reproducer)
I'm experiencing this exact same problem with both Qpid and Proton. Link to upstream bug. Workaround may be to explicitly specify version desired: FIND_PACKAGE(PythonLibs 2.7 REQUIRED) (In reply to comment #3) > Link to upstream bug. Workaround may be to explicitly specify version > desired: > > FIND_PACKAGE(PythonLibs 2.7 REQUIRED) This does not work. Specifying 2.7 still results in the 3.3 libraries being returned. Specifying 2.7 only requires at least 2.7, not exactly 2.7. Well, looking at the FindPython*.cmake files, they actually use the minimum version in a way that they only check versions with the same major version number, which might not really be the way this is supposed to work, but it makes sense to do it that way for Python. So I'm not sure why you end up with 3.3 still being found. Does your project set Python_ADDITIONAL_VERSIONS anywhere? This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. This problem still exists in Fedora 19. Any fix / workaround so far? Upstream bug http://public.kitware.com/Bug/view.php?id=13794 has a proposed patch, but otherwise upstream hasn't acted on this issue yet. I've added the patch from the upstream tracker to the rawhide build. It seems to work for me. I'll try to propagate it down when 2.8.12 is released. cmake-2.8.12-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/cmake-2.8.12-1.fc19 Package cmake-2.8.12-2.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing cmake-2.8.12-2.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-18792/cmake-2.8.12-2.fc19 then log in and leave karma (feedback). cmake-2.8.12-2.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. cmake-3.0.0-0.3.rc1 now carries upstream's version of the fix. Let me know if it causes any problems. |