Thanks. I'd just bump if were you. Patching for such a stupid thing doesn't make sense. Jeff Sent from my iPhone
On Nov 10, 2015, at 9:29 AM, Kenneth Raffenetti <[email protected]> wrote:
Looks to be specific to the 2.4.3 tarball, which has an unexpected LT_PACKAGE_VERSION (2.4.2.458.26-92994) in m4/ltversion.m4. We can either put in a workaround or just bump the requirement in the next release.
Thanks for reporting.
Ken
On 11/10/2015 08:54 AM, Jeff Hammond wrote: autogen.sh fails because it says I need "version 2.4.3 or higher required", but I have version 2.4.3 (see below). i upgraded to 2.4.6 and the problem went away.
Anyways, this isn't a blocker but it seems to be weird logic that it happens.
Jeff
[jrhammo@bowman-rps git]$ ./autogen.sh
####################################
## Replicating confdb (and similar)
####################################
syncing 'src/mpl' --> 'src/pm/hydra/mpl'
syncing 'confdb' --> 'src/mpi/romio/confdb'
syncing 'confdb' --> 'src/mpl/confdb'
syncing 'confdb' --> 'src/pm/hydra/confdb'
syncing 'confdb' --> 'src/pm/hydra/mpl/confdb'
syncing 'confdb' --> 'test/mpi/confdb'
####################################
## Checking user environment
####################################
Verifying the location of autogen.sh... done
Checking if autotools are in the same location... yes, all in /storage/home_intel/jrhammo/TOOLS
Checking for autoconf version... >= 2.67
Checking for automake version... >= 1.15
Checking for libtool version... bad libtool installation
You either do not have libtool in your path or it is too old
(version 2.4.3 or higher required). You may be able to use
libtool --version
Unfortunately, there is no standard format for the version output and
it changes between autotools versions. In addition, some versions of
autoconf choose among many versions and provide incorrect output).
[jrhammo@bowman-rps git]$ libtool --version
libtool (GNU libtool) 2.4.3
Written by Gordon Matzigkeit, 1996
Copyright (C) 2014 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
-- Jeff Hammond [email protected] <mailto:[email protected]> http://jeffhammond.github.io/
_______________________________________________ To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/devel
To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/devel