Hi David, First of all, beautiful name... :-)
Well I'll try if I can pass a default path to find_libraries() function. The idea is finding the libraries in the same path pointed by PYTHON_LIBRARY_DIR variable in CMake file. Let me check this.. Cheers, David On 7 April 2014 21:06, Nielsen, David L. (ARC-TI)[Stinger Ghaffarian Technologies Inc. (SGT Inc.)] <[email protected]> wrote: > Hello NuPIC, > > We are having trouble getting the cmake to run correctly. We're building > as root and unable to follow the directions in the README.md up till that > point but we get the following error when trying to run 'cmake ../..' > > CMake Error at > /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:70 (MESSAGE): > Could NOT find PythonLibs (missing: PYTHON_LIBRARIES) > Call Stack (most recent call first): > /usr/share/cmake/Modules/FindPythonLibs.cmake:102 > (FIND_PACKAGE_HANDLE_STANDARD_ARGS) > CMakeLists.txt:378 (find_package) > > Any idea why we're unable to find PYTHON_LIBRARIES? > > We can get around this with : > > cmake -DPYTHON_LIBRARY=/usr/bin/python ../.. > > This allows cmake and make to complete but then we get a segmentation > fault when running the c++ tests. After a bit of digging we were able to > find this happens when attempting to load the following shared object, > which exists and the path is correct: > > /root/nta/eng/lib/libcpp_region.so > > What might be causing this segfault? > > Thanks, > David & Ritchie > > _______________________________________________ > nupic mailing list > [email protected] > http://lists.numenta.org/mailman/listinfo/nupic_lists.numenta.org > > -- David Ragazzi OS Community Commiter Numenta.org -- "I think James Connonly, the Irish revolutionary, is right when he says that the only prophets are those who make their future. So we're not anticipating , we're working for it."
_______________________________________________ nupic mailing list [email protected] http://lists.numenta.org/mailman/listinfo/nupic_lists.numenta.org
