On Jan 6, 2015, at 9:52 PM, Ralph Castain <r...@open-mpi.org> wrote: > The 1.12 series had a set of problems caused by a changeover in the > maintainers, so it should never be used. I’m not sure if any of those issues > are behind this problem, but it could be so. > > Anyway, I think pretty much all of us are using automake 1.14 by this time. > We can discuss how far up to move the requirement, but I think 1.14 would be > the right place.
Fair enough. I don't think we should change the set used to generate 1.8 series tarballs, though. I think it's a good policy to keep the same autotools tuple for the entire series, unless there's a good reason to change. As Dave noted, our default on our Cisco dev cluster is AM 1.13.3. Probably just because that was the most recent version when we last did maintenance on our AM toolchain. It's easy enough for us to update, though. Another point would probably be to update http://www.open-mpi.org/source/building.php to say that the versions listed for master are a minimum version -- devs can use whatever they want (that works :-) ). The other table lines list what tuple is used to create those tarballs. Also note that per https://github.com/open-mpi/ompi/issues/311, we cannot upgrade past LT 2.4.2 right now. This looks like a bug in LT itself (not OMPI), but I don't have a workaround/solution to go beyond LT 2.4.2 right now (and I think it's not high priority... yet). In conclusion: I'll bump the AM version for master on building.php to be 1.13.3 because I know for a fact that it works. If we want to move it higher than that, I don't have too strong an opinion. :-) I think all the other versions for master are fine. -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
