Another data point: I just bootstrapped with Automake 1.14.1, and got the same result (i.e., ls -l before configure, the "hooks" directory is NOT there, run configure, ls -l and the "hooks" directory IS there).
I'm guessing something changed elsewhere in the toolchain on RHEL7/SLES12(beta) that is causing this problem. Bert: how is the "hooks" directory normally created? Do you have some specific .m4 that creates it? Or is it a side-effect of something in configure? On Jul 24, 2014, at 9:42 AM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> wrote: > On Jul 24, 2014, at 8:55 AM, Bert Wesarg <bert.wes...@tu-dresden.de> wrote: > >> But the dep rules should already ensure this, as it creates the .deps >> directory at the end of configure. Though if this is not guaranteed to >> happen (maybe it depends on the used compiler) than we would need to ensure >> it in the makefile itself. > > FWIW, if I: > > - expand last night's v1.8 nightly tarball on a RHEL 6.5 machine > - look in ompi/contrib/vt/vt/tools/vtunify/mpi, > *** the hooks subdirectory is NOT there *** > - run configure > - look in ompi/contrib/vt/vt/tools/vtunify/mpi, > *** the hooks subdirectory IS there *** > > So at least for AC 2.69, AM 1.12.2, LT 2.4.2, M4 1.4.16 (which is what is > used to make the 1.8 tarball) on RHEL 6.x, it works as expected. > > Is this not true on a RHEL 7 or SLES 12 (beta) machine? > > Or is this not true for some different set of gnu autotools to bootstrap the > tarball? > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > _______________________________________________ > 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/2014/07/15248.php -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/