He really needs to "see" what files FindBoost is trying to locate. The best way is to hack into the FindBoost.cmake file and add some debugging outputs and run cmake to find out exactly what FindBoost.cmake is really looking for.

So down around line 449, insert the following:
MESSAGE (STATUS "${Boost_LIB_PREFIX}boost_${COMPONENT}$ {_boost_COMPILER}${_boost_MULTITHREADED}-${_boost_ABI_TAG}-$ {Boost_LIB_VERSION}") MESSAGE (STATUS "${Boost_LIB_PREFIX}boost_${COMPONENT}$ {_boost_COMPILER}${_boost_MULTITHREADED}${_boost_STATIC_TAG}$ {_boost_ABI_TAG}-${Boost_LIB_VERSION}") MESSAGE (STATUS "${Boost_LIB_PREFIX}boost_${COMPONENT}$ {_boost_MULTITHREADED}-${_boost_ABI_TAG}") MESSAGE (STATUS "${Boost_LIB_PREFIX}boost_${COMPONENT}$ {_boost_MULTITHREADED}${_boost_STATIC_TAG}${_boost_ABI_TAG}") MESSAGE (STATUS "${Boost_LIB_PREFIX}boost_${COMPONENT}-$ {_boost_ABI_TAG}")

and then rerun cmake on your problem machine and send the output to the list.

--
Mike Jackson   Senior Research Engineer
Innovative Management & Technology Services


On Jun 25, 2008, at 4:52 PM, Alan W. Irwin wrote:

On 2008-06-25 14:46-0500 Ravi Tej Kavalipati wrote:

Library File Name Listing on Problem Machine :

http://www.cct.lsu.edu/~cdekate/ problem_boost_library_list.txt<http://www.cct.lsu.edu/%7Ecdekate/ problem_boost_library_list.txt>

Library File Name Listing on Working Machine :

http://www.cct.lsu.edu/~cdekate/ working_boost_library_list.txt<http://www.cct.lsu.edu/%7Ecdekate/ working_boost_library_list.txt>

I know little about Boost, but as a service for those with a deeper interest
in this thread here is the diff of those two files.

--- problem_boost_library_list.txt      2008-06-25 12:39:58.000000000 -0700
+++ working_boost_library_list.txt      2008-06-25 12:37:17.000000000 -0700
@@ -26,8 +26,6 @@
 libboost_date_time-gcc42-sd-1_35.a
 libboost_date_time-gcc42-sd.a
 libboost_date_time-gcc42.so
-libboost_date_time.so.1
-libboost_date_time.so.1.32.0
 libboost_filesystem-gcc42-1_35.a
 libboost_filesystem-gcc42-1_35.so
 libboost_filesystem-gcc42-1_35.so.1.35.0
@@ -56,8 +54,6 @@
 libboost_filesystem-gcc42-sd-1_35.a
 libboost_filesystem-gcc42-sd.a
 libboost_filesystem-gcc42.so
-libboost_filesystem.so.1
-libboost_filesystem.so.1.32.0
 libboost_graph-gcc42-1_35.a
 libboost_graph-gcc42-1_35.so
 libboost_graph-gcc42-1_35.so.1.35.0
@@ -86,34 +82,6 @@
 libboost_graph-gcc42-sd-1_35.a
 libboost_graph-gcc42-sd.a
 libboost_graph-gcc42.so
-libboost_iostreams-gcc42-1_35.a
-libboost_iostreams-gcc42-1_35.so
-libboost_iostreams-gcc42-1_35.so.1.35.0
-libboost_iostreams-gcc42.a
-libboost_iostreams-gcc42-d-1_35.a
-libboost_iostreams-gcc42-d-1_35.so
-libboost_iostreams-gcc42-d-1_35.so.1.35.0
-libboost_iostreams-gcc42-d.a
-libboost_iostreams-gcc42-d.so
-libboost_iostreams-gcc42-mt-1_35.a
-libboost_iostreams-gcc42-mt-1_35.so
-libboost_iostreams-gcc42-mt-1_35.so.1.35.0
-libboost_iostreams-gcc42-mt.a
-libboost_iostreams-gcc42-mt-d-1_35.a
-libboost_iostreams-gcc42-mt-d-1_35.so
-libboost_iostreams-gcc42-mt-d-1_35.so.1.35.0
-libboost_iostreams-gcc42-mt-d.a
-libboost_iostreams-gcc42-mt-d.so
-libboost_iostreams-gcc42-mt-s-1_35.a
-libboost_iostreams-gcc42-mt-s.a
-libboost_iostreams-gcc42-mt-sd-1_35.a
-libboost_iostreams-gcc42-mt-sd.a
-libboost_iostreams-gcc42-mt.so
-libboost_iostreams-gcc42-s-1_35.a
-libboost_iostreams-gcc42-s.a
-libboost_iostreams-gcc42-sd-1_35.a
-libboost_iostreams-gcc42-sd.a
-libboost_iostreams-gcc42.so
 libboost_prg_exec_monitor-gcc42-1_35.a
 libboost_prg_exec_monitor-gcc42-1_35.so
 libboost_prg_exec_monitor-gcc42-1_35.so.1.35.0
@@ -142,8 +110,6 @@
 libboost_prg_exec_monitor-gcc42-sd-1_35.a
 libboost_prg_exec_monitor-gcc42-sd.a
 libboost_prg_exec_monitor-gcc42.so
-libboost_prg_exec_monitor.so.1
-libboost_prg_exec_monitor.so.1.32.0
 libboost_program_options-gcc42-1_35.a
 libboost_program_options-gcc42-1_35.so
 libboost_program_options-gcc42-1_35.so.1.35.0
@@ -172,38 +138,6 @@
 libboost_program_options-gcc42-sd-1_35.a
 libboost_program_options-gcc42-sd.a
 libboost_program_options-gcc42.so
-libboost_program_options.so.1
-libboost_program_options.so.1.32.0
-libboost_python-gcc42-1_35.a
-libboost_python-gcc42-1_35.so
-libboost_python-gcc42-1_35.so.1.35.0
-libboost_python-gcc42.a
-libboost_python-gcc42-d-1_35.a
-libboost_python-gcc42-d-1_35.so
-libboost_python-gcc42-d-1_35.so.1.35.0
-libboost_python-gcc42-d.a
-libboost_python-gcc42-d.so
-libboost_python-gcc42-mt-1_35.a
-libboost_python-gcc42-mt-1_35.so
-libboost_python-gcc42-mt-1_35.so.1.35.0
-libboost_python-gcc42-mt.a
-libboost_python-gcc42-mt-d-1_35.a
-libboost_python-gcc42-mt-d-1_35.so
-libboost_python-gcc42-mt-d-1_35.so.1.35.0
-libboost_python-gcc42-mt-d.a
-libboost_python-gcc42-mt-d.so
-libboost_python-gcc42-mt-s-1_35.a
-libboost_python-gcc42-mt-s.a
-libboost_python-gcc42-mt-sd-1_35.a
-libboost_python-gcc42-mt-sd.a
-libboost_python-gcc42-mt.so
-libboost_python-gcc42-s-1_35.a
-libboost_python-gcc42-s.a
-libboost_python-gcc42-sd-1_35.a
-libboost_python-gcc42-sd.a
-libboost_python-gcc42.so
-libboost_python.so.1
-libboost_python.so.1.32.0
 libboost_regex-gcc42-1_35.a
 libboost_regex-gcc42-1_35.so
 libboost_regex-gcc42-1_35.so.1.35.0
@@ -232,8 +166,6 @@
 libboost_regex-gcc42-sd-1_35.a
 libboost_regex-gcc42-sd.a
 libboost_regex-gcc42.so
-libboost_regex.so.1
-libboost_regex.so.1.32.0
 libboost_serialization-gcc42-1_35.a
 libboost_serialization-gcc42-1_35.so
 libboost_serialization-gcc42-1_35.so.1.35.0
@@ -290,8 +222,6 @@
 libboost_signals-gcc42-sd-1_35.a
 libboost_signals-gcc42-sd.a
 libboost_signals-gcc42.so
-libboost_signals.so.1
-libboost_signals.so.1.32.0
 libboost_system-gcc42-1_35.a
 libboost_system-gcc42-1_35.so
 libboost_system-gcc42-1_35.so.1.35.0
@@ -336,8 +266,6 @@
 libboost_test_exec_monitor-gcc42-s.a
 libboost_test_exec_monitor-gcc42-sd-1_35.a
 libboost_test_exec_monitor-gcc42-sd.a
-libboost_test_exec_monitor.so.1
-libboost_test_exec_monitor.so.1.32.0
 libboost_thread-gcc42-mt-1_35.a
 libboost_thread-gcc42-mt-1_35.so
 libboost_thread-gcc42-mt-1_35.so.1.35.0
@@ -352,8 +280,6 @@
 libboost_thread-gcc42-mt-sd-1_35.a
 libboost_thread-gcc42-mt-sd.a
 libboost_thread-gcc42-mt.so
-libboost_thread.so.1
-libboost_thread.so.1.32.0
 libboost_unit_test_framework-gcc42-1_35.a
 libboost_unit_test_framework-gcc42-1_35.so
 libboost_unit_test_framework-gcc42-1_35.so.1.35.0
@@ -382,8 +308,6 @@
 libboost_unit_test_framework-gcc42-sd-1_35.a
 libboost_unit_test_framework-gcc42-sd.a
 libboost_unit_test_framework-gcc42.so
-libboost_unit_test_framework.so.1
-libboost_unit_test_framework.so.1.32.0
 libboost_wave-gcc42-1_35.a
 libboost_wave-gcc42-1_35.so
 libboost_wave-gcc42-1_35.so.1.35.0

So all Boost libraries on the good machine are also on the problem machine.

I am now wondering whether any of those many extra Boost libraries on the
problem machine are somehow confusing FindBoost.cmake on that machine?

Alan
__________________________
Alan W. Irwin

Astronomical research affiliation with Department of Physics and Astronomy,
University of Victoria (astrowww.phys.uvic.ca).

Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); PLplot scientific plotting software package (plplot.org); the libLASi project (unifont.org/lasi); the Loads of
Linux Links project (loll.sf.net); and the Linux Brochure Project
(lbproject.sf.net).
__________________________

Linux-powered Science
__________________________
_______________________________________________
CMake mailing list
[email protected]
http://www.cmake.org/mailman/listinfo/cmake



_______________________________________________
CMake mailing list
[email protected]
http://www.cmake.org/mailman/listinfo/cmake

Reply via email to