I looked at this thread in a little more detail... The question below is a little moot because of the change that was done to v1.8, but please humor me anyway. :-)
Macro: I think you told me before, but I forget, so please refresh my memory: I seem to recall that there's a reason you're invoking autogen in a tarball, but I don't remember what it is. I ask because in all POSIX cases at least, end users should be able to just untar, configure, make, make install -- they don't/shouldn't run autogen). I.e., it doesn't matter what version of Libtool end users have installed (or not!) because we bootstrapped the tarball with a Libtool version that we know works. Even more specifically: the error you're running in to should not have happened with a plain tarball -- the only cases where I can think of it happening would be if you got a git clone and ran autogen, or if you got a tarball and (re-)ran autogen. > On Apr 18, 2015, at 3:59 PM, Marco Atzeri <marco.atz...@gmail.com> wrote: > > tomorrow is fine . > I am testing octave-4.0.0-rc3 today > ;-) > > > On 4/18/2015 9:13 PM, Ralph Castain wrote: >> I am planning on rc2 on Monday, if you’d prefer to wait >> >> >>> On Apr 18, 2015, at 9:30 AM, Marco Atzeri <marco.atz...@gmail.com> wrote: >>> >>> Are you planning another rc or I should test the git stable repository ? >>> > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2015/04/17270.php -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
