Yo Brian
I updated this morning and hit a few problems. I found I was using autoconf
2.60, so I had to update to automake 1.10 as you indicated. However, once I
did that, I still couldn't build due to the following errors:
configure.in:1994: warning: macro `AM_PROG_LIBTOOL' not found in library
[Running] autoheader
[Running] autoconf
configure.in:1997: error: possibly undefined macro: AM_PROG_LIBTOOL
If this token and others are legitimate, please use m4_pattern_allow.
See the Autoconf documentation.
-------------------------------------------------------------------------
It seems that the execution of "autoconf" has failed. See above for
the specific error message that caused it to abort.
This *MAY* be caused by an older version of one of the required
packages. Please make sure you are using at least the following
versions:
GNU Autoconf 2.59
GNU Automake 1.9.6
GNU Libtool 1.5.16
-------------------------------------------------------------------------
Error running autogen.sh -l in romio. Aborting.
pn1169403:~/openmpi/trunk rhc$
I am running:
Autoconf 2.60
Automake 1.10
Libtool 1.5.22
Any suggestions?
Ralph
On 11/29/06 2:17 PM, "Brian W Barrett" <bbarr...@lanl.gov> wrote:
> Hi all -
>
> Just wanted to give everyone a heads up that there will be two
> changes to the build system that should have minimal impact on
> everyone, but are worth noting:
>
> 1) If you are using Autoconf 2.60 or later, you *MUST* be using
> Automake 1.10 or later. Most people are still using AC 2.59,
> so this should have zero impact on the group.
>
> 2) We will now be checking to make sure that the C++, F77, F90,
> and ObjC compilers can link against the C compiler. This
> should clean up some of the amorphous errors people have been
> getting when they do something like: 'CFLAGS=-m32 CXXFLAGS=-m64',
> usually by not specifying one of the two...
>
> Brian
> _______________________________________________
> devel mailing list
> de...@open-mpi.org
> http://www.open-mpi.org/mailman/listinfo.cgi/devel
