[petsc-dev] configure failure
Barry Smith
bsmith at mcs.anl.gov
Thu Jul 13 13:18:51 CDT 2017
p4est configure should provide an option to not run compiled code and instead have needed values passed in as configure arguments.
> On Jul 13, 2017, at 1:07 PM, Matthew Knepley <knepley at gmail.com> wrote:
>
> On Thu, Jul 13, 2017 at 12:32 PM, Mark Adams <mfadams at lbl.gov> wrote:
>
> Are you cross-compiling there?
>
> configure:4469: checking whether we are cross compiling
> configure:4477: ftn -o conftest -g -O -fp-model fast -qopt-report=5 -qopenmp-simd conftest.f -Wl,-rpath,/global/homes/m/madams/petsc/arch-cori-knl-opt-intel/lib -L/global/homes/m/madams/petsc/arch-cori-knl-opt-intel/lib -lflapack -Wl,-rpath,/global/homes/m/madams/petsc/arch-cori-knl-opt-intel/lib -L/global/homes/m/madams/petsc/arch-cori-knl-opt-intel/lib -lfblas -L/opt/cray/pe/mpt/7.4.4/gni/sma/lib64 -L/opt/cray/pe/libsci/16.09.1/INTEL/15.0/mic_knl/lib -L/opt/cray/pe/hdf5-parallel/1.10.0/INTEL/15.0/lib -L/opt/cray/dmapp/default/lib64 -L/opt/cray/pe/mpt/7.4.4/gni/mpich-intel/16.0/lib -L/usr/common/software/darshan/3.1.4/lib -L/opt/cray/rca/2.1.6_g2c60fbf-2.265/lib64 -L/opt/cray/alps/6.3.4-2.21/lib64 -L/opt/cray/xpmem/2.1.1_gf9c9084-2.38/lib64 -L/opt/cray/dmapp/7.1.1-39.37/lib64 -L/opt/cray/pe/pmi/5.0.10-1.0000.11050.0.0.ari/lib64 -L/opt/cray/ugni/6.0.15-2.2/lib64 -L/opt/cray/udreg/2.3.2-7.54/lib64 -L/opt/cray/pe/atp/2.1.0/libApp -L/opt/cray/wlm_detect/1.2.1-3.10/lib64 -L/usr/common/software/h5part/1.6.6/lib -L/opt/intel/compilers_and_libraries_2017.2.174/linux/compiler/lib/intel64 -L/opt/intel/compilers_and_libraries_2017.2.174/linux/mkl/lib/intel64 -L/opt/intel/compilers_and_libraries_2017.2.174/linux/compiler/lib/intel64_lin -L/usr/lib64/gcc/x86_64-suse-linux/4.8 -L/usr/x86_64-suse-linux/lib -lhdf5hl_fortran_parallel -lhdf5_fortran_parallel >&5
> ifort: remark #10397: optimization reports are generated in *.optrpt files in the output location
> configure:4481: $? = 0
> configure:4488: ./conftest
> libhugetlbfs [cori10:124117]: WARNING: Hugepage size 2097152 unavailable
> Please verify that both the operating system and the processor support Intel(R) AVX512F, ADX, RDSEED, AVX512ER, AVX512PF and AVX512CD instructions.
>
> Matt
>
> On Thu, Jul 13, 2017 at 12:21 PM, Matthew Knepley <knepley at gmail.com> wrote:
> Toby, this is from the p4est configure:
>
> o---------------------------------------
> | Checking MPI and related programs
> o---------------------------------------
> checking whether we are using MPI... yes
> checking whether we are using MPI I/O... yes
> checking whether we are using MPI_Init_thread... yes
> checking for mpiexec... no
> checking for mpirun... no
> configure: F77 set to ftn
> configure: FC set to ftn
> configure: CC set to cc
> configure: CXX set to CC
> checking whether the Fortran 77 compiler works... yes
> checking for Fortran 77 compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling...configure: error: in `/global/u2/m/madams/petsc/arch-cori-knl-opt-intel/externalpackages/git.p4est':
> configure: error: cannot run Fortran 77 compiled programs.
> If you meant to cross compile, use `--host'.
> See `config.log' for more details
>
> Mark, gets us /global/u2/m/madams/petsc/arch-cori-knl-opt-intel/externalpackages/git.p4est/config.log
>
> Thanks,
>
> Matt
>
>
> On Thu, Jul 13, 2017 at 11:15 AM, Mark Adams <mfadams at lbl.gov> wrote:
> I always get this error on Cori at NERSC, KNL, but I can usually rerun configure and it runs the second time. Well, I can't seem to get this to work now.
> Thanks,
> Mark
>
>
>
> --
> What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.
> -- Norbert Wiener
>
> http://www.caam.rice.edu/~mk51/
>
>
>
>
> --
> What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.
> -- Norbert Wiener
>
> http://www.caam.rice.edu/~mk51/
More information about the petsc-dev
mailing list