<div dir="ltr"><div>Thanks, I'll check it out. Glad you are unbound by the rising and setting of the sun :-)</div><div><br></div><div>Brian</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Sep 3, 2019 at 11:47 PM Smith, Barry F. <<a href="mailto:bsmith@mcs.anl.gov">bsmith@mcs.anl.gov</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
--with-blaslapack-libs="-framework Accelerate" also works (though is not needed). <br>
<br>
Using COPTFLAGS="-framework Accelerate" doesn't work because hypre doesn't use the C flags when linking the shared libraries hence the -framework Accelerate is not passed to the linker.<br>
<br>
Barry<br>
<br>
<br>
> On Sep 4, 2019, at 12:41 AM, Brian Van Straalen <<a href="mailto:bvstraalen@lbl.gov" target="_blank">bvstraalen@lbl.gov</a>> wrote:<br>
> <br>
> Thanks Barry. that gets me further. now it seems the COPTFLAGS are not being propagated from PETSC to HYPRE. I have -framework Accelerate in my COPTFLAGS, but HYPRE still fails looking for BLAS and LAPACK routines. _dgetri, _dgetrs, and so on. Or does PETSc, and Hypre, and SUPERLU all pull in their own blas and lapack source code and this is from me disabling Fortran? I can't use Fortran in PETSc since sowing does not work on OSX as PETSc configures it (claims "configure: error: cannot run C compiled programs." but I know that is not true. I suspect sowing has linux-isms see attached log). <br>
> <br>
> is there some way to have PETSc configure just run through and configure things, and have a make command make things? I have to keep re-issuing the configure command, which prevents me from debugging a build errors. I'm about two days into this port to OSX.... <br>
> <br>
> Brian<br>
> <br>
> <br>
> On Tue, Sep 3, 2019 at 9:35 PM Smith, Barry F. <<a href="mailto:bsmith@mcs.anl.gov" target="_blank">bsmith@mcs.anl.gov</a>> wrote:<br>
> <br>
> Ahh, the --download-c2html is not needed; it is used only when building all of the PETSc documentation including html versions of the source.<br>
> <br>
> For some reason it's configure is not doing a good job of selecting cpp. Over the years it has been amazingly portable, I guess Apple just went a bit too far.<br>
> <br>
> Anyways just run without that option,<br>
> <br>
> Barry<br>
> <br>
> <br>
> <br>
> > On Sep 3, 2019, at 11:24 PM, Brian Van Straalen via petsc-users <<a href="mailto:petsc-users@mcs.anl.gov" target="_blank">petsc-users@mcs.anl.gov</a>> wrote:<br>
> > <br>
> > I can attach the config log. mpi breaks for yet other reasons so I was trying to simplify things sufficiently. <br>
> > <br>
> > if I put mpi back in and take the compiler choices out, I still end up with failure on CPP. It seems determined to look for "/lib/cpp" which is only correct for linux.<br>
> > <br>
> > <br>
> > <br>
> > <br>
> > On Tue, Sep 3, 2019 at 9:11 PM Balay, Satish <<a href="mailto:balay@mcs.anl.gov" target="_blank">balay@mcs.anl.gov</a>> wrote:<br>
> > On Wed, 4 Sep 2019, Balay, Satish via petsc-users wrote:<br>
> > <br>
> > > On Tue, 3 Sep 2019, Brian Van Straalen via petsc-users wrote:<br>
> > > <br>
> > > > pulling from git PETSC and on master branch.<br>
> > > > <br>
> > > > ./configure CPP=/usr/bin/cpp<br>
> > > > ===============================================================================<br>
> > > > Configuring PETSc to compile on your system<br>
> > > > <br>
> > > > ===============================================================================<br>
> > > > TESTING: checkCPreprocessor from<br>
> > > > config.setCompilers(config/BuildSystem/config/setCompilers.py:592)<br>
> > > > <br>
> > > > *******************************************************************************<br>
> > > > UNABLE to CONFIGURE with GIVEN OPTIONS (see configure.log for<br>
> > > > details):<br>
> > > > -------------------------------------------------------------------------------<br>
> > > > Cannot find a C preprocessor<br>
> > > > *******************************************************************************<br>
> > > <br>
> > > Its best to send configure.log<br>
> > > <br>
> > > > <br>
> > > > <br>
> > > > <br>
> > > > Brian<br>
> > > > <br>
> > > > my configure script<br>
> > > > <br>
> > > > configure_options = [<br>
> > > > # '--with-mpi-dir=/usr/local/opt/open-mpi',<br>
> > <br>
> > Hm - this is commented out anyway. So there is no mpi specified for this build (its a mandatory dependency)? <br>
> > <br>
> > > > '--with-cc=/usr/bin/clang',<br>
> > > > '--with-cpp=/usr/bin/cpp',<br>
> > > > '--with-cxx=/usr/bin/clang++',<br>
> > > <br>
> > > The above 3 options are redundant - when --with-mpi-dir is provided. PETSc configure will pick up mpicc etc from the specified location.<br>
> > > <br>
> > > > '--with-fc=0',<br>
> > > <br>
> > > Hm - this conflicts with --download-mumps etc that require fortran<br>
> > > <br>
> > > Satish<br>
> > > <br>
> > > > 'COPTFLAGS=-g -framework Accelerate',<br>
> > > > 'CXXOPTFLAGS=-g -framework Accelerate',<br>
> > > > 'FOPTFLAGS=-g',<br>
> > > > # '--with-memalign=64',<br>
> > > > '--download-hypre=1',<br>
> > > > '--download-metis=1',<br>
> > > > '--download-parmetis=1',<br>
> > > > '--download-c2html=1',<br>
> > > > '--download-ctetgen',<br>
> > > > # '--download-viennacl',<br>
> > > > # '--download-ml=1',<br>
> > > > '--download-p4est=1',<br>
> > > > '--download-superlu_dist',<br>
> > > > '--download-superlu',<br>
> > > > '--with-cxx-dialect=C++11',<br>
> > > > '--download-mumps=1',<br>
> > > > '--download-scalapack=1',<br>
> > > > # '--download-exodus=1',<br>
> > > > # '--download-ctetgen=1',<br>
> > > > '--download-triangle=1',<br>
> > > > # '--download-pragmatic=1',<br>
> > > > # '--download-eigen=1',<br>
> > > > '--download-zlib',<br>
> > > > '--with-x=1',<br>
> > > > '--with-sowing=0',<br>
> > > > '--with-debugging=1',<br>
> > > > '--with-precision=double',<br>
> > > > 'PETSC_ARCH=arch-macosx-gnu-g',<br>
> > > > '--download-chaco'<br>
> > > > ]<br>
> > > > <br>
> > > > if __name__ == '__main__':<br>
> > > > import sys,os<br>
> > > > sys.path.insert(0,os.path.abspath('config'))<br>
> > > > import configure<br>
> > > > configure.petsc_configure(configure_options)<br>
> > > > <br>
> > > > <br>
> > > > <br>
> > > <br>
> > <br>
> > <br>
> > <br>
> > -- <br>
> > Brian Van Straalen Lawrence Berkeley Lab<br>
> > <a href="mailto:BVStraalen@lbl.gov" target="_blank">BVStraalen@lbl.gov</a> Computational Research<br>
> > (510) 486-4976 Division (<a href="http://crd.lbl.gov" rel="noreferrer" target="_blank">crd.lbl.gov</a>)<br>
> > <configure.log><br>
> <br>
> <br>
> <br>
> -- <br>
> Brian Van Straalen Lawrence Berkeley Lab<br>
> <a href="mailto:BVStraalen@lbl.gov" target="_blank">BVStraalen@lbl.gov</a> Computational Research<br>
> (510) 486-4976 Division (<a href="http://crd.lbl.gov" rel="noreferrer" target="_blank">crd.lbl.gov</a>)<br>
> <configure.log><br>
<br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><span style="font-family:monospace,monospace">Brian Van Straalen Lawrence Berkeley Lab<br><a href="mailto:BVStraalen@lbl.gov" target="_blank">BVStraalen@lbl.gov</a> Computational Research<br>(510) 486-4976 Division (<a href="http://crd.lbl.gov" target="_blank">crd.lbl.gov</a>)</span><br></div></div>