[mpich-discuss] ./maint/updatefiles and configure problems

Dave Goodell goodell at mcs.anl.gov
Mon Feb 15 08:24:06 CST 2010


Yeah, we can add something like this.  There is a version requirement  
specified in the AM_INIT_AUTOMAKE line, but the actual check only  
occurs when automake is run.  So when your maint/updatefiles step  
bails after only running autoconf, you never get the more  
understandable message about version mismatch.

-Dave

On Feb 15, 2010, at 7:27 AM, Jeff Hammond wrote:

> Can ./maint/updatefiles be instrumented to check for that
> compatibility as well (i.e. in addition to autoconf 2.63)?  That would
> help us noobs running a GNU toolchain that's more than three months
> old :)
>
> Thanks,
>
> Jeff
>
> On Sun, Feb 14, 2010 at 10:59 PM, Pavan Balaji <balaji at mcs.anl.gov>  
> wrote:
>>
>> Looks like you don't have automake-1.11.
>>
>>  -- Pavan
>>
>> On 02/14/2010 10:24 PM, Jeff Hammond wrote:
>>> I did the usual "svn update" and ./maint/updatefiles  on the mpich2
>>> trunk but there were problems in the second stage as well as the
>>> subsequent configure step.
>>>
>>> I'm not dependent on this code, so there is no urgency in fixing  
>>> what
>>> I perceive to be a problem.
>>>
>>> Thanks,
>>>
>>> Jeff
>>>
>>> ===============================================================
>>> step 1
>>> ===============================================================
>>> jeff at megatron:/software/mpich/mpich2-trunk> svn update
>>> ...
>>>
>>> ===============================================================
>>> step 2
>>> ===============================================================
>>> jeff at megatron:/software/mpich/mpich2-trunk> ./maint/updatefiles
>>> You have autoconf version 2.63 or greater.
>>> Checking that libtool version is acceptable...
>>> ...
>>> ------------------------------------------------------------------------
>>> running autoreconf in src/pm/hydra
>>> autoreconf: Entering directory `.'
>>> autoreconf: configure.in: not using Gettext
>>> autoreconf: running: aclocal --force -I mpl/confdb
>>> configure.in:181: warning: macro `AM_SUBST_NOTMAKE' not found in  
>>> library
>>> configure.in:182: warning: macro `AM_SUBST_NOTMAKE' not found in  
>>> library
>>> configure.in:183: warning: macro `AM_SUBST_NOTMAKE' not found in  
>>> library
>>> configure.in:195: warning: macro `AM_SUBST_NOTMAKE' not found in  
>>> library
>>> configure.in:231: warning: macro `AM_SUBST_NOTMAKE' not found in  
>>> library
>>> configure.in:237: warning: macro `AM_SUBST_NOTMAKE' not found in  
>>> library
>>> configure.in:238: warning: macro `AM_SUBST_NOTMAKE' not found in  
>>> library
>>> configure.in:239: warning: macro `AM_SUBST_NOTMAKE' not found in  
>>> library
>>> autoreconf: configure.in: tracing
>>> autoreconf: running: libtoolize --copy --force
>>> libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `mpl/ 
>>> confdb'.
>>> libtoolize: copying file `mpl/confdb/ltmain.sh'
>>> libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `mpl/confdb'.
>>> libtoolize: copying file `mpl/confdb/libtool.m4'
>>> libtoolize: copying file `mpl/confdb/ltoptions.m4'
>>> libtoolize: copying file `mpl/confdb/ltsugar.m4'
>>> libtoolize: copying file `mpl/confdb/ltversion.m4'
>>> libtoolize: copying file `mpl/confdb/lt~obsolete.m4'
>>> configure.in:181: warning: macro `AM_SUBST_NOTMAKE' not found in  
>>> library
>>> configure.in:182: warning: macro `AM_SUBST_NOTMAKE' not found in  
>>> library
>>> configure.in:183: warning: macro `AM_SUBST_NOTMAKE' not found in  
>>> library
>>> configure.in:195: warning: macro `AM_SUBST_NOTMAKE' not found in  
>>> library
>>> configure.in:231: warning: macro `AM_SUBST_NOTMAKE' not found in  
>>> library
>>> configure.in:237: warning: macro `AM_SUBST_NOTMAKE' not found in  
>>> library
>>> configure.in:238: warning: macro `AM_SUBST_NOTMAKE' not found in  
>>> library
>>> configure.in:239: warning: macro `AM_SUBST_NOTMAKE' not found in  
>>> library
>>> autoreconf: running: /usr/bin/autoconf --force
>>> configure.in:183: error: possibly undefined macro: AM_SUBST_NOTMAKE
>>>       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
>>>
>>> ===============================================================
>>> step 3
>>> ===============================================================
>>> jeff at megatron:/software/mpich/mpich2-trunk> ./configure CC=gcc  
>>> CXX=g++
>>> F77=gfortran FC=gfortran
>>> --prefix=/software/mpich/gnu-build-mpich2-trunk
>>> --with-thread-package=pthreads --enable-threads=default --enable-f77
>>> --enable-f90 --enable-cxx --enable-romio --enable-smpcoll --enable- 
>>> mpe
>>> --with-pm=hydra
>>> ...
>>> checking boot-strap server... ssh,rsh,fork,slurm,persist
>>> /software/mpich/mpich2-trunk/src/pm/hydra/configure: line 12966:
>>> syntax error near unexpected token `hydra_bss_init_decl'
>>> /software/mpich/mpich2-trunk/src/pm/hydra/configure: line 12966:
>>> `AM_SUBST_NOTMAKE(hydra_bss_init_decl)'
>>>
>>>
>>>
>>
>> --
>> Pavan Balaji
>> http://www.mcs.anl.gov/~balaji
>> _______________________________________________
>> mpich-discuss mailing list
>> mpich-discuss at mcs.anl.gov
>> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss
>>
>
>
>
> -- 
> Jeff Hammond
> Argonne Leadership Computing Facility
> jhammond at mcs.anl.gov / (630) 252-5381
> http://www.linkedin.com/in/jeffhammond
> _______________________________________________
> mpich-discuss mailing list
> mpich-discuss at mcs.anl.gov
> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss



More information about the mpich-discuss mailing list