Right, there are no python 2.7 dependencies in that repo. It was really just for 2.6. --------- Matt Taylor OS Community Flag-Bearer Numenta
On Wed, Feb 12, 2014 at 8:06 AM, Justin Souter <[email protected]> wrote: > > I was able to follow the docs about setting up the .profile file so the > environment is set up. Troubleshooting docs would be great. Also I realize > my set-up is non-standard (Mountain Lion with Xcode 5), but was hoping > issues with that could be overcome. > > As for the python 2.7 dependencies, running: > > git clone https://github.com/numenta/nupic-darwin64/tree/python-2.7 > > Results in: > > fatal: repository > 'https://github.com/numenta/nupic-darwin64/tree/python-2.7/' not found > > > On Feb 12, 2014, at 7:51 AM, Jeff Fohl <[email protected]> wrote: > > The nupic-darwin64 repository does not contain NuPIC - it contains the > python dependencies to run NuPIC on OSX. > > The master branch of this repo is for python 2.6, but there is another > branch for python 2.7: > https://github.com/numenta/nupic-darwin64/tree/python-2.7 > > Austin did a great job setting this up, but I think the README of the > nupic-darwin64 could be a bit more robust, and include some tips for > troubleshooting. For example, I think it needs to tell you to make sure that > the $NUPIC environment variable needs to be set (should point to your NuPIC > code base). I think I might make an issue for this. > > - Jeff > > > On Wed, Feb 12, 2014 at 7:37 AM, Matthew Taylor <[email protected]> wrote: >> >> I'm not sure the darwin-64 repo will help in this case, it is mostly >> for bundled python 2.6 dependencies. I just wish I understood why that >> autoconf error is happening. >> --------- >> Matt Taylor >> OS Community Flag-Bearer >> Numenta >> >> >> On Tue, Feb 11, 2014 at 10:19 PM, Justin Souter >> <[email protected]> wrote: >> > >> > That's all the information it's showing via stdout and in the log. >> > >> > I started with the github.com/numenta/nupic.git repository, not the >> > github.com/numenta/nupic-darwin64. My dim understanding was that these are >> > incompatible. >> > >> > >> > On Feb 11, 2014, at 8:59 PM, [email protected] wrote: >> > >> >> Hm, I haven't seen that error before. Through some cursory web searches >> >> on >> >> "mac os x autoconf failed" it seems there is usually more information >> >> associated with that error. Is this output coming from stdout/stderr or >> >> the >> >> build log file? >> >> >> >> Anyone have any ideas? >> >> >> >> --------- >> >> Matt Taylor >> >> OS Community Flag-Bearer >> >> Numenta >> >> >> >> >> >> On Tue, Feb 11, 2014 at 11:13 AM, Justin Souter >> >> <[email protected]>wrote: >> >> >> >>> Trying to get a Mac OS build going. Using XCode5 on Mountain Lion >> >>> (contrary to the OS X build docs, XCode5 runs fine on 10.8.5). The >> >>> $NUPIC/build.sh step gave me some issues. >> >>> >> >>> First, autom4te could not be found, so I added a symlink in >> >>> /usr/local/bin >> >>> to its location in ../Cellar/autoconf/2.69/bin/autom4te, following the >> >>> pattern of the symlinks for the other tools. >> >>> >> >>> Then another issue came up, which I haven't yet found a solution for. >> >>> It's >> >>> quitting on the autoconf step, though with different errors than I see >> >>> in >> >>> similar list posts. Here's my output: >> >>> >> >>> running libtoolize... >> >>> glibtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, >> >>> `build_system/unix'. >> >>> glibtoolize: copying file `build_system/unix/ltmain.sh' >> >>> glibtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to >> >>> configure.acand >> >>> glibtoolize: rerunning glibtoolize, to keep the correct libtool macros >> >>> in-tree. >> >>> glibtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in >> >>> Makefile.am. >> >>> running aclocal... >> >>> running autoconf... >> >>> Usage: autoconf [-h] [--help] [-m dir] [--macrodir=dir] >> >>> [-l dir] [--localdir=dir] [--version] [template-file] >> >>> autoconf failed. Exiting >> >>> >> >>> >> >>> So I've tried to add the AC_CONFIG_MACRO_DIR suggestion, not knowing >> >>> the >> >>> best place in the file, and I've added the ACLOCAL_AMFLAGS thing, >> >>> neither >> >>> of which helped my issue or silenced those suggestions from >> >>> glibtoolize. >> >>> Seems like autoconf doesn't like its arguments. >> >>> >> >>> My set up: >> >>> >> >>> Mac OS X 10.8.5 >> >>> XCode 5.0.2 >> >>> Python 2.7.2 >> >>> PIP 1.5.2 >> >>> Autoconf 2.13 >> > >> > >> > _______________________________________________ >> > 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 > > > > _______________________________________________ > 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
