Bug 1131949

Summary: CMake may fail to build if '/bin' or '/sbin' is in $PATH
Product: [Fedora] Fedora Reporter: J. Sastre <jsastreh>
Component: cmakeAssignee: Orion Poplawski <orion>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: jreznik, ltinkl, orion, pertusus, pmachata, rdieter
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-20 15:22:34 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 J. Sastre 2014-08-20 11:32:27 UTC
Description of problem:

When building using CMake an error may occur if '/bin' or '/sbin' is in $PATH. bins and libs directories were moved to '/usr' in the past but '/usr/lib{64}' is still reachable through '/lib{64}'. CMake uses $PATH among (many others resources) to set variables regarding prefixes and paths to others components and packages. When searching for these paths CMake consider '/' as a valid search path if '/bin' or '/sbin' are included in $PATH.

Some packages store its <PkgName>-config.cmake files under '/usr/lib64/cmake/<PkgName>/' and since '/' is in the internal search path list of CMake '/lib64/cmake/<PkgName>' is also reachable. Some variables will be affected by this (e.g. CMAKE_CURRENT_LIST_FILE or CMAKE_CURRENT_LIST_DIR). If these vars are used to infer any kind of PREFIX (collada-dom-devel package make use of this mechanism. See https://bugzilla.redhat.com/show_bug.cgi?id=1057985) '/' will be gotten instead of '/usr' and any content other than libs will not be reachable (e.g. '/usr/include' will be looked up on /include).


Version-Release number of selected component (if applicable):
2.8.12.2

Steps to reproduce:
# mkdir /usr/lib64/cmake/mypkg
# echo "message(${CMAKE_CURRENT_LIST_DIR})" > /usr/lib64/cmake/mypkg/mypkg-config.cmake
$ cd ; mkdir tmp ; cd tmp
$ echo -e "cmake_minimum_required(VERSION 2.8.3)\nproject(mypkg)\nfind_package(MYPKG)"
$ cmake ./


Actual results:
/lib64/cmake/mypkg

Expected results:
/usr/lib64/cmake/mypkg

Additional info:

Possible solutions

* Consider using CMAKE_CURRENT_LIST_XXX vars to deduce prefixes as a bad practice and avoid its use (some different packages involved) 
* Reinforce path search mechanism in CMake to detect this situation.
* May be not really a bug. Removing '/bin' and '/sbin' from $PATH works well.

Comment 1 Orion Poplawski 2014-08-20 15:22:34 UTC
Yeah, don't use CMAKE_CURRENT_* variables in the installed cmake files.  Set the variables explicitly at install time (when they are known).  You might look at libcmocka for an example.