I've already replied to this issue Try a fresh build - and do not reuse --prefix for different version builds.
Have you tried doing this? Satish On Tue, 31 Oct 2017, Manav Bhatia wrote: > Thanks, Barry. > > Does this also address the mumps compilation issue that I had shared in the > same thread: > > mumps_c.c:307:53: error: no member named 'nnz' in 'CMUMPS_STRUC_C'; did you > mean 'nz'? > mumps_par->n=0; mumps_par->nz=0; mumps_par->nnz=0; > mumps_par->nz_loc=0; mumps_par->nnz_loc=0; > mumps_par->nelt=0;mumps_par->instance_number=0;mumps_par->deficiency=0;mumps_par->lwk_user=0;mumps_par->size_schur=0;mumps_par->lrhs=0; > mumps_par->lredrhs=0; mumps_par->nrhs=0; mumps_par->nz_rhs=0; > mumps_par->lsol_loc=0; > ^~~ > nz > /Users/manav/Documents/codes/numerical_lib/petsc/include/cmumps_c.h:56:20: > note: 'nz' declared here > MUMPS_INT nz; > ^ > mumps_c.c:307:92: error: no member named 'nnz_loc' in 'CMUMPS_STRUC_C'; did > you mean 'nz_loc'? > mumps_par->n=0; mumps_par->nz=0; mumps_par->nnz=0; > mumps_par->nz_loc=0; mumps_par->nnz_loc=0; > mumps_par->nelt=0;mumps_par->instance_number=0;mumps_par->deficiency=0;mumps_par->lwk_user=0;mumps_par->size_schur=0;mumps_par->lrhs=0; > mumps_par->lredrhs=0; mumps_par->nrhs=0; mumps_par->nz_rhs=0; > mumps_par->lsol_loc=0; > > ^~~~~~~ > > nz_loc > /Users/manav/Documents/codes/numerical_lib/petsc/include/cmumps_c.h:62:20: > note: 'nz_loc' declared here > MUMPS_INT nz_loc; > ^ > mumps_c.c:419:42: error: no member named 'nnz' in 'CMUMPS_STRUC_C'; did you > mean 'nz'? > &(mumps_par->nz), &(mumps_par->nnz), irn, &irn_avail, jcn, > &jcn_avail, a, &a_avail, > ^~~ > nz > /Users/manav/Documents/codes/numerical_lib/petsc/include/cmumps_c.h:56:20: > note: 'nz' declared here > MUMPS_INT nz; > ^ > mumps_c.c:420:46: error: no member named 'nnz_loc' in 'CMUMPS_STRUC_C'; did > you mean 'nz_loc'? > &(mumps_par->nz_loc), &(mumps_par->nnz_loc), irn_loc, > &irn_loc_avail, jcn_loc, &jcn_loc_avail, > ^~~~~~~ > nz_loc > /Users/manav/Documents/codes/numerical_lib/petsc/include/cmumps_c.h:62:20: > note: 'nz_loc' declared here > MUMPS_INT nz_loc; > ^ > mumps_c.c:419:29: warning: incompatible pointer types passing 'int *' to > parameter of type 'int64_t *' (aka 'long long *') > [-Wincompatible-pointer-types] > &(mumps_par->nz), &(mumps_par->nnz), irn, &irn_avail, jcn, > &jcn_avail, a, &a_avail, > ^~~~~~~~~~~~~~~~~ > mumps_c.c:99:28: note: passing argument to parameter 'nnz' here > MUMPS_INT8 *nnz, > ^ > mumps_c.c:420:33: warning: incompatible pointer types passing 'int *' to > parameter of type 'int64_t *' (aka 'long long *') > [-Wincompatible-pointer-types] > &(mumps_par->nz_loc), &(mumps_par->nnz_loc), irn_loc, > &irn_loc_avail, jcn_loc, &jcn_loc_avail, > ^~~~~~~~~~~~~~~~~~~~~ > mumps_c.c:107:28: note: passing argument to parameter 'nnz_loc' here > MUMPS_INT8 *nnz_loc, > ^ > 2 warnings and 4 errors generated. > > > > On Oct 31, 2017, at 4:25 PM, Smith, Barry F. <bsm...@mcs.anl.gov> wrote: > > > > > > Manav, > > > > Thanks for reporting the problem > > > > Fande, > > > > Thanks for the pointer. > > > > Satish determined the correct long term fix and it is in the branch > > barry/fix-lto_library-option-maint and will be put in the maint branch and > > master branch if it passes the testing tonight. > > > > Barry > > > > > >> On Oct 30, 2017, at 11:36 AM, Kong, Fande <fande.k...@inl.gov> wrote: > >> > >> We had exactly the same issue when upgraded compilers. I guess this is > >> somehow related to gfortran. A simple way to work around for us is to > >> change if with_rpath: to if False at line 54 of > >> config/BuildSystem/config/libraries.py. > >> > >> Not sure if it works for you. > >> > >> Fande, > >> > >> > >> > >> > >> On Mon, Oct 30, 2017 at 10:14 AM, Manav Bhatia <bhatiama...@gmail.com> > >> wrote: > >> Hi, > >> > >> I am trying to install pets 3.8 on a new MacBook machine with OS 10.13. I > >> have installed openmpi from macports and I am getting this error on > >> configuration. Attached is also the configure.log file. > >> > >> I am not sure how to proceed with this. Any advice will be greatly > >> appreciated! > >> > >> Regards, > >> Manav > >> > >> =============================================================================== > >> Configuring PETSc to compile on your system > >> > >> =============================================================================== > >> =============================================================================== > >> > >> > >> ***** WARNING: Using default optimization C flags -g -O3 > >> > >> > >> You might consider manually setting optimal optimization flags > >> for your system with > >> > >> COPTFLAGS="optimization flags" see > >> config/examples/arch-*-opt.py for examples > >> > >> > >> =============================================================================== > >> > >> > >> =============================================================================== > >> > >> > >> ***** WARNING: Using default C++ optimization flags -g -O3 > >> > >> > >> You might consider manually setting optimal optimization flags > >> for your system with > >> > >> CXXOPTFLAGS="optimization flags" see > >> config/examples/arch-*-opt.py for examples > >> > >> > >> =============================================================================== > >> > >> > >> =============================================================================== > >> > >> > >> ***** WARNING: Using default FORTRAN optimization flags -g -O > >> > >> > >> You might consider manually setting optimal optimization flags > >> for your system with > >> > >> FOPTFLAGS="optimization flags" see > >> config/examples/arch-*-opt.py for examples > >> > >> > >> =============================================================================== > >> > >> > >> =============================================================================== > >> > >> > >> WARNING! Compiling PETSc with no debugging, this should > >> > >> > >> only be done for timing and production runs. All > >> development should > >> > >> be done when configured using > >> --with-debugging=1 > >> > >> > >> =============================================================================== > >> > >> > >> TESTING: checkCLibraries from > >> config.compilers(config/BuildSystem/config/compilers.py:171) > >> > >> > >> ******************************************************************************* > >> UNABLE to CONFIGURE with GIVEN OPTIONS (see configure.log for > >> details): > >> ------------------------------------------------------------------------------- > >> C libraries cannot directly be used from Fortran > >> ******************************************************************************* > >> > >> > >> > >> > >> > >> > > > >
