MantisBT - CMake
View Issue Details
0010933CMakeCMakepublic2010-07-03 10:372012-07-09 06:52
Andrey Rahmatullin 
Brad King 
normalminoralways
closedfixed 
CMake-2-8 
CMake 2.8.8 
0010933: CMake tries to link against -llibarchive
SET(CMAKE_TAR_LIBRARIES libarchive) causes CMake to link against "libarchive", not "archive":

/usr/bin/ld: cannot find -llibarchive
collect2: ld returned 1 exit status
make[2]: *** [Source/libCMakeLib.so] Error 1
No tags attached.
Issue History
2010-07-03 10:37Andrey RahmatullinNew Issue
2010-07-13 09:18Bill HoffmanNote Added: 0021378
2010-07-13 09:19Bill HoffmanStatusnew => assigned
2010-07-13 09:19Bill HoffmanAssigned To => Bill Hoffman
2010-07-14 03:03Andrey RahmatullinNote Added: 0021389
2010-07-14 03:06Andrey RahmatullinNote Added: 0021390
2012-01-10 17:12Brad KingNote Added: 0028246
2012-01-11 03:36Andrey RahmatullinNote Added: 0028254
2012-01-11 08:33Brad KingStatusassigned => resolved
2012-01-11 08:33Brad KingFixed in Version => CMake 2.8.8
2012-01-11 08:33Brad KingResolutionopen => fixed
2012-01-11 08:33Brad KingAssigned ToBill Hoffman => Brad King
2012-07-09 06:52David ColeNote Added: 0029951
2012-07-09 06:52David ColeStatusresolved => closed

Notes
(0021378)
Bill Hoffman   
2010-07-13 09:18   
How did you configure CMake?
(0021389)
Andrey Rahmatullin   
2010-07-14 03:03   
Well, I've added -DCMAKE_USE_SYSTEM_LIBARCHIVE=1 to cmake_bootstrap_system_libs= in bootstrap and used bootstrap --system-libs. I've ignored the message about missing FindLibArchive.cmake because it is not needed here and to build cmake with system libarchive I've needed only to change "libarchive" to "archive" in the line mentioned in this report.
(0021390)
Andrey Rahmatullin   
2010-07-14 03:06   
I've looked at the Debian patch in 0010923, it solves the same problem in a more proper way (it changes "libarchive" to the FindLibArchive.cmake result).
(0028246)
Brad King   
2012-01-10 17:12   
Is this still a problem in CMake's Git master? Lots of stuff has changed since this issue was reported.
(0028254)
Andrey Rahmatullin   
2012-01-11 03:36   
No, it looks fixed.
(0029951)
David Cole   
2012-07-09 06:52   
Closing resolved issues that have not been updated in more than 4 months.