MantisBT - CMake
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0013446CMakeCMakepublic2012-07-31 11:252016-06-10 14:31
Reporterkdawgud 
Assigned ToKitware Robot 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionmoved 
Platform64-bit LinuxOSCentOS OS Version6.3 64-bit
Product VersionCMake 2.8.8 
Target VersionFixed in Version 
Summary0013446: find_package(Boost) does not map library paths correctly
DescriptionThe boost library find places libraries in /usr/lib64/lib64 instead of just /usr/lib64. Reverting to 2.8.3 fixes the problem. I have not tried verions 2.8.4 through 2.8.7.

Steps To ReproduceLink against boost libraries using find_package(Boost) in a CMake project using CentOS 64-bit.
Additional InformationSee here for more information:
http://stackoverflow.com/questions/9948375/cmake-find-package-succeeds-but-returns-wrong-path [^]
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2012-07-31 11:25kdawgudNew Issue
2012-10-20 21:20John MorrisNote Added: 0031287
2016-06-10 14:28Kitware RobotNote Added: 0042098
2016-06-10 14:28Kitware RobotStatusnew => resolved
2016-06-10 14:28Kitware RobotResolutionopen => moved
2016-06-10 14:28Kitware RobotAssigned To => Kitware Robot
2016-06-10 14:31Kitware RobotStatusresolved => closed

Notes
(0031287)
John Morris   
2012-10-20 21:20   
This problem occurs when using some older versions of boost with cmake-2.8.6-rc2 or later, where the boost package finding code was changed. The EL6 boost package is version 1.41.

The problem can be worked around by specifying '-DBoost_NO_BOOST_CMAKE=ON' on the cmake command line.

The actual commit where this problem is introduced is 7da796d1fdd7cca07df733d010cd343f6f8787a9, and can be viewed here:

http://cmake.org/gitweb?p=cmake.git;a=commit;h=7da796d1fdd7cca07df733d010cd343f6f8787a9 [^]
(0042098)
Kitware Robot   
2016-06-10 14:28   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current CMake Issues page linked in the banner at the top of this page.