I still can't build MPICH2 at Argonne. If I use the stock environment on login3 or elephant, I get a failure with autoconf being 2.61. If I use the MPICH2_xxx_DIR environment variables that used to work, I get ... Found ./configure.in; executing make configure target (cd . && /home/chan/autoconf/2.63/bin/autoheader -I ./confdb && \ \ /home/chan/autoconf/2.63/bin/autoconf -I ./confdb ) running third-party initialization Remember to add `AC_PROG_LIBTOOL' to `configure.ac'. You should add the contents of `/usr/share/aclocal/libtool.m4' to `aclocal.m4'. Putting files in AC_CONFIG_AUX_DIR, `config'. libtoolize: `config.guess' exists: use `--force' to overwrite libtoolize: `config.sub' exists: use `--force' to overwrite libtoolize: `ltmain.sh' exists: use `--force' to overwrite autoreconf2.50: Entering directory `.' autoreconf2.50: configure.ac: not using Gettext autoreconf2.50: running: /home/chan/automake/1.11/bin/aclocal --force - I config -I m4 autoreconf2.50: configure.ac: tracing autoreconf2.50: configure.ac: not using Libtool autoreconf2.50: running: /home/chan/autoconf/2.63/bin/autoconf --force configure.ac:417: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. autoreconf2.50: /home/chan/autoconf/2.63/bin/autoconf failed with exit status: 1 login3:/homes/gropp/projects/software/mpich2(5) If I set MPICH_LIBTOOL_DIR to Anthony's libtool, I get the same. There is no MPICH2_LIBTOOLIZE in maint/updatefiles login3:/homes/gropp/projects/software/mpich2(5) grep LIBTOOLIZE maint/ updatefiles LIBTOOLIZE=$libtoolize export LIBTOOLIZE libtoolize=${LIBTOOLIZE:-libtoolize} login3:/homes/gropp/projects/software/mpich2(6) How do you build MPICH2 at Argonne? (and could you put this info into the instructions on the wiki) Bill On Dec 9, 2009, at 4:15 PM, Pavan Balaji wrote:
Bill,
We modified all the scripts to accept MPICH2_LIBTOOLIZE. On my machine, for example, I don't have LIBTOOL set, and it works correctly for me. But then, I have all the autotools installed in the same location; that might be a preferred way for autotools anyway, so setting LIBTOOL might not be required.
-- Pavan
On 12/09/2009 09:48 AM, William Gropp wrote:
I discovered that the environment variable LIBTOOL needs to be properly set - though there's no documentation about this, I believe that libtoolize may require this. I've made some updates to updatefiles to include this and to check on the version of libtool. I'll check it in after a few more tests.
Bill
On Nov 18, 2009, at 4:53 PM, Anthony Chan wrote:
Oh, Pavan also had me add "libtoolize" to autogen.sh in hwloc:
% cat src/pm/hydra/tools/bind/hwloc/hwloc/autogen.sh : libtoolize autoreconf -ivf
The libtoolize line is not in svn. After adding libtoolize in hwloc/autogen.sh, maint/updatefiles was able to run to completion.... Also, it does require libtool 2.2.6. The build tool failed with libtool 2.2.4....
A.Chan
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign
-- Pavan Balaji http://www.mcs.anl.gov/~balaji
William Gropp Deputy Director for Research Institute for Advanced Computing Applications and Technologies Paul and Cynthia Saylor Professor of Computer Science University of Illinois Urbana-Champaign