Marek, thanks for the feedback. I did are you said,
then tried to build. Getting a different set of errors...
below is my attempt, sorry its long, figured it might
be useful to see...
Scott, at the end, is what you asked. Changing the
PATH env variable changed where its looks and
in doing so, is now finding the newer versions.
But perhaps they are not the correct versions?
At the end, you can see what versions its using.
Does that look correct?
Thanks!
Patrick
bash-3.2$ export PATH=/usr/local/bin:$PATH
bash-3.2$ ./build.sh
Warning: directory "/Users/Patrick/nta/eng" already exists and may contain
(old) data. Consider removing it.
Warning: directory "/tmp/ntabuild" already exists and may contain (old) data.
Consider removing it.
/tmp/ntabuild ~/nupic-master
Updated 6 libraries in arch darwin64
Generating build files for unix
/Users/Patrick/nupic-master/build_system/post_build
/Users/Patrick/nupic-master/lang/py/bindings/engine_internal
/Users/Patrick/nupic-master/lang/py/support
/Users/Patrick/nupic-master/nta/algorithms
/Users/Patrick/nupic-master/nta/apps/htmtest
/Users/Patrick/nupic-master/nta/engine
/Users/Patrick/nupic-master/nta/math
/Users/Patrick/nupic-master/nta/ntypes
/Users/Patrick/nupic-master/nta/os
/Users/Patrick/nupic-master/nta/regions
/Users/Patrick/nupic-master/nta/test
/Users/Patrick/nupic-master/nta/types
/Users/Patrick/nupic-master/nta/utils
/Users/Patrick/nupic-master/py/bindings/algorithms
/Users/Patrick/nupic-master/py/bindings/iorange
/Users/Patrick/nupic-master/py/bindings/math
/Users/Patrick/nupic-master/py/cpp_region
/Users/Patrick/nupic-master/qa/testeverything
Processed 18 projects
Done generating build files for unix
Running autogen...
---- output -----
/usr/local/bin/aclocal
/usr/local/bin/autoconf
/usr/local/bin/automake
/usr/local/bin/autoreconf
/usr/bin/glibtoolize
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.ac and
glibtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
glibtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
running aclocal...
running autoconf...
configure.ac:68: error: possibly undefined macro: AC_DISABLE_STATIC
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.ac:69: error: possibly undefined macro: AC_ENABLE_SHARED
configure.ac:72: error: possibly undefined macro: AC_LIBTOOL_DLOPEN
configure.ac:74: error: possibly undefined macro: AC_PROG_LIBTOOL
autoconf failed. Exiting
---- end of output -----
/usr/local/bin/aclocal
/usr/local/bin/autoconf
/usr/local/bin/automake
/usr/local/bin/autoreconf
/usr/bin/glibtoolize
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.ac and
glibtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
glibtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
running aclocal...
running autoconf...
configure.ac:68: error: possibly undefined macro: AC_DISABLE_STATIC
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.ac:69: error: possibly undefined macro: AC_ENABLE_SHARED
configure.ac:72: error: possibly undefined macro: AC_LIBTOOL_DLOPEN
configure.ac:74: error: possibly undefined macro: AC_PROG_LIBTOOL
autoconf failed. Exiting
Command: '/bin/bash build_system/unix/autogen.sh'
Traceback (most recent call last):
File "/Users/Patrick/nupic-master/build_system/setup.py", line 209, in
<module>
utils.runCommand(["/bin/bash", command], outputLogLevel=logging.INFO)
File "/Users/Patrick/nupic-master/build_system/pybuild/utils.py", line 150,
in runCommand
raise RunCommandException("\n %s Command: '%s'" % (allOutput, commandLine))
pybuild.utils.RunCommandException:
/usr/local/bin/aclocal
/usr/local/bin/autoconf
/usr/local/bin/automake
/usr/local/bin/autoreconf
/usr/bin/glibtoolize
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.ac and
glibtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
glibtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
running aclocal...
running autoconf...
configure.ac:68: error: possibly undefined macro: AC_DISABLE_STATIC
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
configure.ac:69: error: possibly undefined macro: AC_ENABLE_SHARED
configure.ac:72: error: possibly undefined macro: AC_LIBTOOL_DLOPEN
configure.ac:74: error: possibly undefined macro: AC_PROG_LIBTOOL
autoconf failed. Exiting
Command: '/bin/bash build_system/unix/autogen.sh'
bash-3.2$ which automake
/usr/local/bin/automake
bash-3.2$ automake --version
automake (GNU automake) 1.13.2
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv2+: GNU GPL version 2 or later
<http://gnu.org/licenses/gpl-2.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by Tom Tromey <[email protected]>
and Alexandre Duret-Lutz <[email protected]>.
bash-3.2$ autoconf --version
autoconf (GNU Autoconf) 2.69
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+/Autoconf: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>, <http://gnu.org/licenses/exceptions.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Written by David J. MacKenzie and Akim Demaille.
On Aug 12, 2013, at 4:35 PM, Scott Purdy wrote:
> Patrick, you can use the "which" command to figure out where it is getting
> each thing from. For instance:
>
> $ which automake
> /usr/local/bin/automake
>
>
> On Mon, Aug 12, 2013 at 4:30 PM, Marek Otahal <[email protected]> wrote:
> Hi Patrick,
>
>
> On Tue, Aug 13, 2013 at 1:21 AM, Patrick Higgins <[email protected]> wrote:
> I am attempting to build NuPIC in OS X 10.6.8
> I have installed mp-gcc-4.7 using Macports and
> it is located in /opt/local/bin
> I have installed pip 2.6 using easy_install
> autoconf 2.6 and automake 1.14 which are all
> three located in /usr/local/bin
>
> I see aclocal and aclocal-1.10 in /Developer/usr/bin
> but when I do a whereis aclocal, it reports /usr/bin
> I see it there as well... these are older versions that
> won't work with nupic.
>
> And the version in /Developer/usr/bin is the correct one? (new enough to
> build)
>
> When I try to build nupic, it is not finding the
> correct automake or autoconf, and I don't think
> its finding the correct pip either. I don't really
> know enough about how to configure things
> so that it knows where the dependencies are
> located. Its finding the default installs of everything
> instead of the newer versions that nupic requires.
> I'm pretty sure I need to keep the older ones around
> so I don't break OS X, but that shouldn't be a problem
> if I can correctly tell the nupic build file where the
> newer versions are located.
>
> Am I installing things in the wrong place or do
> I just need to change a file or $PATH to tell it
> where to find what it needs?
>
> I cant tell you if this is a proper way to install in Mac (but it seems good
> to me).
> Yes, just try
> export PATH=/usr/local/bin:$PATH
> before building nupic and you should be fine. (add any other paths needed to
> the beginning too, like the /Developer/usr/bin )
>
> Thanks, any help would be much appreciated.
>
>
>
> Patrick
> Cheers and let us know how far you go with that,
> Mark
_______________________________________________
nupic mailing list
[email protected]
http://lists.numenta.org/mailman/listinfo/nupic_lists.numenta.org
