Re: [OMPI users] possibly undefined macro: AC_PROG_LIBTOOL

2012-01-04 Thread Jeff Squyres
I don't know if I've tried explicitly with 2.67, but I'd be surprised if it doesn't recognize AC_PROG_LIBTOOL. Also note that AC_PROG_LIBTOOL comes from Libtool, not Autoconf. FWIW, I've seen this kind of error when AC/AM/LT are not installed to the same tree. If they're installed to differen

Re: [OMPI users] possibly undefined macro: AC_PROG_LIBTOOL

2011-12-29 Thread Ralph Castain
I use 2.68 and 2.65 and have no problems. Could be that 2.67 has a problem - perhaps try with one of the other levels? On Dec 29, 2011, at 5:14 PM, Dmitry N. Mikushin wrote: > OK, apparently that were various backports. And now I have only one > autoconf installed, and it is: > > marcusmae@tes

Re: [OMPI users] possibly undefined macro: AC_PROG_LIBTOOL

2011-12-29 Thread Dmitry N. Mikushin
OK, apparently that were various backports. And now I have only one autoconf installed, and it is: marcusmae@teslatron:~/Programming/openmpi-r24785$ autoconf --version autoconf (GNU Autoconf) 2.67 marcusmae@teslatron:~/Programming/openmpi-r24785$ autoreconf --version autoreconf (GNU Autoconf) 2.6

Re: [OMPI users] possibly undefined macro: AC_PROG_LIBTOOL

2011-12-29 Thread Ralph Castain
On Dec 29, 2011, at 3:39 PM, Dmitry N. Mikushin wrote: > No, that was autoREconf, and all they are below 2.65: > > marcusmae@teslatron:~/Programming/openmpi-r24785$ ls /usr/bin/autoreconf > autoreconf autoreconf2.13 autoreconf2.50 autoreconf2.59 autoreconf2.64 > > And default one points

Re: [OMPI users] possibly undefined macro: AC_PROG_LIBTOOL

2011-12-29 Thread Dmitry N. Mikushin
No, that was autoREconf, and all they are below 2.65: marcusmae@teslatron:~/Programming/openmpi-r24785$ ls /usr/bin/autoreconf autoreconf autoreconf2.13 autoreconf2.50 autoreconf2.59 autoreconf2.64 And default one points to 2.50: marcusmae@teslatron:~/Programming/openmpi-r24785$ autoreco

Re: [OMPI users] possibly undefined macro: AC_PROG_LIBTOOL

2011-12-29 Thread Ralph Castain
Strange - if you look at your original output, autoconf is identified as 2.50 - a version that is way too old for us. However, what you just sent now shows 2.67, which would be fine. Why the difference? On Dec 29, 2011, at 3:27 PM, Dmitry N. Mikushin wrote: > Hi Ralph, > > URL: http://svn.op

Re: [OMPI users] possibly undefined macro: AC_PROG_LIBTOOL

2011-12-29 Thread Dmitry N. Mikushin
Hi Ralph, URL: http://svn.open-mpi.org/svn/ompi/trunk Repository Root: http://svn.open-mpi.org/svn/ompi Repository UUID: 63e3feb5-37d5-0310-a306-e8a459e722fe Revision: 24785 Node Kind: directory Schedule: normal Last Changed Author: rhc Last Changed Rev: 24785 Last Changed Date: 2011-06-17 22:01:2

Re: [OMPI users] possibly undefined macro: AC_PROG_LIBTOOL

2011-12-29 Thread Ralph Castain
Are you doing this on a subversion checkout? Of which branch? Did you check your autotoll versions to ensure you meet the minimum required levels? The requirements differ by version. On Dec 29, 2011, at 2:52 PM, Dmitry N. Mikushin wrote: > Dear Open MPI Community, > > I need a custom OpenMPI b

[OMPI users] possibly undefined macro: AC_PROG_LIBTOOL

2011-12-29 Thread Dmitry N. Mikushin
Dear Open MPI Community, I need a custom OpenMPI build. While running ./autogen.pl on Debian Squeeze, there is an error: --- Found autogen.sh; running... autoreconf2.50: Entering directory `.' autoreconf2.50: configure.in: not using Gettext autoreconf2.50: running: aclocal --force -I m4 autorecon