Ideally this would be built into the cmake instructions - a new user shouldn't have to type this!
--Subutai On Thu, Mar 20, 2014 at 8:19 AM, Austin Marshall <[email protected]> wrote: > On my system (OS X Mavericks), I can run: > > cmake -DPYTHON_LIBRARY=`python -c "import sysconfig; print > sysconfig.get_config_var('LIBDIR'),"`/libpython2.7.dylib $NUPIC > > which yields: > > > /System/Library/Frameworks/Python.framework/Versions/2.7/lib/libpython2.7.dylib > > for the Python lib. > > > On Thu, Mar 20, 2014 at 2:51 AM, Pradeepto Bhattacharya < > [email protected]> wrote: > >> Hi Austin, >> >> >> On Wed, Mar 19, 2014 at 8:26 PM, Austin Marshall <[email protected]>wrote: >> >>> This happens when there's a problem in linking the right version of >>> python during build. If you know where libpython2.7.so is, you can >>> explicitly specify the location by adding the following command-line >>> argument to the call to cmake: >>> >>> -DPYTHON_LIBRARY=<path to libpython2.7.so> >>> >>> You may need to `apt-get install python-devel` or whatever the right >>> ubuntu package is for the python development libs. >>> >>> >> What is the equivalent of that in OS X? >> >> >> Regards, >> >> Pradeepto >> -- >> Pradeepto Kumar Bhattacharya >> KDE e.V. Board of Director | Proud KDE Contributor >> The KDE Project : http://www.kde.org >> >> _______________________________________________ >> nupic mailing list >> [email protected] >> http://lists.numenta.org/mailman/listinfo/nupic_lists.numenta.org >> >> > > _______________________________________________ > nupic mailing list > [email protected] > http://lists.numenta.org/mailman/listinfo/nupic_lists.numenta.org > >
_______________________________________________ nupic mailing list [email protected] http://lists.numenta.org/mailman/listinfo/nupic_lists.numenta.org
