Yup, looks fine in the nightly (1.9a1r30319) tarball. -Paul
On Fri, Jan 17, 2014 at 7:14 AM, Jeff Squyres (jsquyres) <jsquy...@cisco.com > wrote: > Paul -- > > Looks like this wasn't actually fixed until r30305. > > > On Jan 16, 2014, at 11:31 PM, Paul Hargrove <phhargr...@lbl.gov> wrote: > > > > > The following commit claimed to have resolved the OSHMEM_SETUP_CFLAGS > issues: > > > > r30286 | miked | 2014-01-14 05:23:44 -0800 (Tue, 14 Jan 2014) | 5 lines > > > > OSHMEM: fix fortran selection logic and refactoring > > refactoring inspired by this thread: > http://www.open-mpi.org/community/lists/devel/2014/01/13744.php > > fix oshmem fortran selection logic, Thanks to Paul for info > > Refs #3763 > > > > However the past couple nightly tarballs (1.9a1r30298 and 1.9a1r30302) > > produce output like the following: > > > > *** Compiler flags > > checking which of CFLAGS are ok for debugger modules... -DNDEBUG > > checking for debugger extra CFLAGS... -g > > > /global/homes/h/hargrove/GSCRATCH/OMPI/openmpi-trunk-linux-x86_64-pgi-12.10/openmpi-1.9a1r30302/configure: > line 285176: OSHMEM_SETUP_CFLAGS: command not found > > > > -Paul > > > > > > -- > > Paul H. Hargrove phhargr...@lbl.gov > > Future Technologies Group > > Computer and Data Sciences Department Tel: +1-510-495-2352 > > Lawrence Berkeley National Laboratory Fax: +1-510-486-6900 > > _______________________________________________ > > devel mailing list > > de...@open-mpi.org > > http://www.open-mpi.org/mailman/listinfo.cgi/devel > > > -- > 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 > http://www.open-mpi.org/mailman/listinfo.cgi/devel > -- Paul H. Hargrove phhargr...@lbl.gov Future Technologies Group Computer and Data Sciences Department Tel: +1-510-495-2352 Lawrence Berkeley National Laboratory Fax: +1-510-486-6900
