Re: [OMPI devel] Build system changes
Thanks Ralf! Much appreciated. On 11/30/06 8:33 AM, "Ralf Wildenhues"wrote: > * Ralph Castain wrote on Thu, Nov 30, 2006 at 04:12:16PM CET: >> That could be the problem. I had to update automake, and unfortunately >> Darwin Ports hasn't reached that level yet. So I had to build and install >> automake by hand under my own bin directory. But libtool etc are all in >> /usr/bin. > > Then that's the most likely cause. > > * Ralph Castain wrote on Thu, Nov 30, 2006 at 04:10:35PM CET: >> m4 version is 1.4.2 > > Updating is advisable. M4 1.4.8 is the current version. It has > many bugfixes over 1.4.2, and there are a couple of tricky cases > where the latter is known to fail (in conjunction with autoconf). > > If you excuse a small plug: Automake 1.10 and (unreleased) Autoconf 2.62 > will both help to eliminate a large part of config.status execution time, > compared with the 1.9.6/2.59 combo (OpenMPI was used for testing here): > http://lists.gnu.org/archive/html/autoconf-patches/2006-11/msg00035.html > > Cheers, > Ralf > ___ > devel mailing list > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel
Re: [OMPI devel] Build system changes
* Ralph Castain wrote on Thu, Nov 30, 2006 at 04:12:16PM CET: > That could be the problem. I had to update automake, and unfortunately > Darwin Ports hasn't reached that level yet. So I had to build and install > automake by hand under my own bin directory. But libtool etc are all in > /usr/bin. Then that's the most likely cause. * Ralph Castain wrote on Thu, Nov 30, 2006 at 04:10:35PM CET: > m4 version is 1.4.2 Updating is advisable. M4 1.4.8 is the current version. It has many bugfixes over 1.4.2, and there are a couple of tricky cases where the latter is known to fail (in conjunction with autoconf). If you excuse a small plug: Automake 1.10 and (unreleased) Autoconf 2.62 will both help to eliminate a large part of config.status execution time, compared with the 1.9.6/2.59 combo (OpenMPI was used for testing here): http://lists.gnu.org/archive/html/autoconf-patches/2006-11/msg00035.html Cheers, Ralf
Re: [OMPI devel] Build system changes
That could be the problem. I had to update automake, and unfortunately Darwin Ports hasn't reached that level yet. So I had to build and install automake by hand under my own bin directory. But libtool etc are all in /usr/bin. I'll give your suggestion a shot later - gotta run. Thanks Ralph On 11/30/06 8:06 AM, "Ralf Wildenhues"wrote: >> * Ralph Castain wrote on Thu, Nov 30, 2006 at 03:55:05PM CET: >>> >>> 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. > > Another question: does the aclocal from Automake 1.10 find the > libtool.m4 file from your Libtool installation? IOW, if Libtool > and Automake are not installed below the same $prefix, then you > need to do something: either put the path to libtool.m4 in the > file $automake_prefix/share/aclocal/dirlist, or pass some -I > parameters to aclocal. > > Hope that helps. > > Cheers, > Ralf > ___ > devel mailing list > de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/devel
Re: [OMPI devel] Build system changes
> * Ralph Castain wrote on Thu, Nov 30, 2006 at 03:55:05PM CET: > > > > 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. Another question: does the aclocal from Automake 1.10 find the libtool.m4 file from your Libtool installation? IOW, if Libtool and Automake are not installed below the same $prefix, then you need to do something: either put the path to libtool.m4 in the file $automake_prefix/share/aclocal/dirlist, or pass some -I parameters to aclocal. Hope that helps. Cheers, Ralf
Re: [OMPI devel] Build system changes
* Ralph Castain wrote on Thu, Nov 30, 2006 at 03:55:05PM CET: > > 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. > I am running: > > Autoconf 2.60 > Automake 1.10 > Libtool 1.5.22 Which version of m4 do you use? Did libtoolize throw an error (earlier in the autogen output)? Cheers, Ralf
Re: [OMPI devel] Build system changes
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"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