[OMPI users] possibly undefined macro: AC_PROG

Discussion:

[OMPI users] possibly undefined macro: AC_PROG_LIBTOOL

Dmitry N. Mikushin

2011-12-29 21:52:37 UTC

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
autoreconf2.50: configure.in: tracing
autoreconf2.50: configure.in: not using Libtool
autoreconf2.50: running: /usr/bin/autoconf --force
configure.in:113: error: possibly undefined macro: AC_PROG_LIBTOOL
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
autoreconf2.50: /usr/bin/autoconf failed with exit status: 1
Command failed: ./autogen.sh

It's a bit confusing, because automake, libtool, autoconf are
installed. What might be the other reasons of this error?

Thanks,
- Dima.

Ralph Castain

2011-12-29 21:56:08 UTC

Permalink

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.

Post by Dmitry N. Mikushin
Dear Open MPI Community,
I need a custom OpenMPI build. While running ./autogen.pl on Debian
--- Found autogen.sh; running...
autoreconf2.50: Entering directory `.'
autoreconf2.50: configure.in: not using Gettext
autoreconf2.50: running: aclocal --force -I m4
autoreconf2.50: configure.in: tracing
autoreconf2.50: configure.in: not using Libtool
autoreconf2.50: running: /usr/bin/autoconf --force
configure.in:113: error: possibly undefined macro: AC_PROG_LIBTOOL
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
autoreconf2.50: /usr/bin/autoconf failed with exit status: 1
Command failed: ./autogen.sh
It's a bit confusing, because automake, libtool, autoconf are
installed. What might be the other reasons of this error?
Thanks,
- Dima.
_______________________________________________
users mailing list
http://www.open-mpi.org/mailman/listinfo.cgi/users

Dmitry N. Mikushin

2011-12-29 22:27:23 UTC

Permalink

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:23 +0400 (Fri, 17 Jun 2011)

1. Checking tool versions

Searching for autoconf
Found autoconf version 2.67; checking version...
Found version component 2 -- need 2
Found version component 67 -- need 65
==> ACCEPTED
Searching for libtoolize
Found libtoolize version 2.2.6b; checking version...
Found version component 2 -- need 2
Found version component 2 -- need 2
Found version component 6b -- need 6b
==> ACCEPTED
Searching for automake
Found automake version 1.11.1; checking version...
Found version component 1 -- need 1
Found version component 11 -- need 11
Found version component 1 -- need 1
==> ACCEPTED

Post by 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.

_______________________________________________
users mailing list
http://www.open-mpi.org/mailman/listinfo.cgi/users

Ralph Castain

2011-12-29 22:31:55 UTC

Permalink

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?

Post by 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:23 +0400 (Fri, 17 Jun 2011)
1. Checking tool versions
Searching for autoconf
Found autoconf version 2.67; checking version...
Found version component 2 -- need 2
Found version component 67 -- need 65
==> ACCEPTED
Searching for libtoolize
Found libtoolize version 2.2.6b; checking version...
Found version component 2 -- need 2
Found version component 2 -- need 2
Found version component 6b -- need 6b
==> ACCEPTED
Searching for automake
Found automake version 1.11.1; checking version...
Found version component 1 -- need 1
Found version component 11 -- need 11
Found version component 1 -- need 1
==> ACCEPTED

_______________________________________________
users mailing list
http://www.open-mpi.org/mailman/listinfo.cgi/users

Dmitry N. Mikushin

2011-12-29 22:39:25 UTC

Permalink

No, that was autoREconf, and all they are below 2.65:

***@teslatron:~/Programming/openmpi-r24785$ ls /usr/bin/autoreconf
autoreconf autoreconf2.13 autoreconf2.50 autoreconf2.59 autoreconf2.64

And default one points to 2.50:

***@teslatron:~/Programming/openmpi-r24785$ autoreconf -help
Usage: /usr/bin/autoreconf2.50 [OPTION]... [DIRECTORY]...

I don't know why, probably that's the default Debian Squeeze setup?

- D.

Post by 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?

_______________________________________________
users mailing list
http://www.open-mpi.org/mailman/listinfo.cgi/users

Ralph Castain

2011-12-29 22:46:12 UTC

Permalink

Post by Dmitry N. Mikushin
autoreconf autoreconf2.13 autoreconf2.50 autoreconf2.59 autoreconf2.64
Usage: /usr/bin/autoreconf2.50 [OPTION]... [DIRECTORY]...
I don't know why, probably that's the default Debian Squeeze setup?

Probably - but that's no good. It should be the same level as autoconf as the two are packaged together to avoid incompatibilities like you are hitting here. Did you install autoconf yourself? If so, can you point autoreconf to the corresponding binary?

Post by Dmitry N. Mikushin
- D.

_______________________________________________
users mailing list
http://www.open-mpi.org/mailman/listinfo.cgi/users

Dmitry N. Mikushin

2011-12-30 00:14:42 UTC

Permalink

OK, apparently that were various backports. And now I have only one
autoconf installed, and it is:

***@teslatron:~/Programming/openmpi-r24785$ autoconf --version
autoconf (GNU Autoconf) 2.67

***@teslatron:~/Programming/openmpi-r24785$ autoreconf --version
autoreconf (GNU Autoconf) 2.67

However:

6. Processing autogen.subdirs directories

=== Processing subdir:
/home/marcusmae/Programming/openmpi-r24785/opal/mca/event/libevent207/libevent
--- Found autogen.sh; running...
autoreconf: Entering directory `.'
autoreconf: configure.in: not using Gettext
autoreconf: running: aclocal --force -I m4
autoreconf: configure.in: tracing
autoreconf: configure.in: not using Libtool
autoreconf: running: /usr/bin/autoconf --force
configure.in:113: error: possibly undefined macro: AC_PROG_LIBTOOL
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
autoreconf: /usr/bin/autoconf failed with exit status: 1
Command failed: ./autogen.sh

Does it work for you with 2.67?

Thanks,
- D.

Post by Ralph Castain

autoreconf autoreconf2.13 autoreconf2.50 autoreconf2.59 autoreconf2.64
Usage: /usr/bin/autoreconf2.50 [OPTION]... [DIRECTORY]...
I don't know why, probably that's the default Debian Squeeze setup?

- D.

_______________________________________________
users mailing list
http://www.open-mpi.org/mailman/listinfo.cgi/users

Ralph Castain

2011-12-30 00:24:20 UTC

Permalink

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?

Post by Dmitry N. Mikushin
OK, apparently that were various backports. And now I have only one
autoconf (GNU Autoconf) 2.67
autoreconf (GNU Autoconf) 2.67
6. Processing autogen.subdirs directories
/home/marcusmae/Programming/openmpi-r24785/opal/mca/event/libevent207/libevent
--- Found autogen.sh; running...
autoreconf: Entering directory `.'
autoreconf: configure.in: not using Gettext
autoreconf: running: aclocal --force -I m4
autoreconf: configure.in: tracing
autoreconf: configure.in: not using Libtool
autoreconf: running: /usr/bin/autoconf --force
configure.in:113: error: possibly undefined macro: AC_PROG_LIBTOOL
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
autoreconf: /usr/bin/autoconf failed with exit status: 1
Command failed: ./autogen.sh
Does it work for you with 2.67?
Thanks,
- D.

Post by Ralph Castain

Post by Dmitry N. Mikushin
- D.

_______________________________________________
users mailing list
http://www.open-mpi.org/mailman/listinfo.cgi/users

Jeff Squyres

2012-01-04 12:26:58 UTC

Permalink

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 different trees (i.e., with a different --prefix value when you run configure to install them), you'll almost certainly run into this kind of problem.

I'm not sure how Debian Squeeze installs the autotools packages, but if it supports multiple backports of those same packages simultaneously, they could well be installed to different directories, and therefore there might be some restrictions on installing / using them correctly.

FWIW, I just FTP those 4 packages separately from my OS (AC, AM, LT, M4) and configure/make install them myself to a separate side directory (e.g., $HOME/autotools). That prevents all these kind of OS packaging issues.

Post by 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?

Post by Ralph Castain

Post by Dmitry N. Mikushin
- D.

_______________________________________________
users mailing list
http://www.open-mpi.org/mailman/listinfo.cgi/users

--
Jeff Squyres
***@cisco.com
For corporate legal information go to:
http://www.cisco.com/web/about/doing_business/legal/cri/