[petsc-users] Error during PETSc build on Edison
Satish Balay
balay at mcs.anl.gov
Mon Jan 29 22:12:04 CST 2018
1. cray provides prebuilt petsc libraries. Does that work for you?
2. verylikely you need:
--with-clib-autodetect=0
--with-cxxlib-autodetect=0
LIBS=-lstdc++
If it doesn't work - send configure.log
Satish
On Tue, 30 Jan 2018, Amneet Bhalla wrote:
> Hi,
>
> I am trying to build PETSc (v3.7.7) locally in my home directory on NERSC
> (Edison).
> However, I am getting the following error during the configuration stage.
>
> ===============================================================================
>
> TESTING: checkFortranNameMangling from
> config.compilers(config/BuildSystem/config/compilers.py:653)
>
> *******************************************************************************
>
> UNABLE to CONFIGURE with GIVEN OPTIONS (see configure.log for
> details):
>
> -------------------------------------------------------------------------------
>
> Unknown Fortran name mangling: Are you sure the C and Fortran compilers are
> compatible?
>
> Perhaps one is 64 bit and one is 32 bit?
>
> -------------------------------------------------------------------------------
>
> Unknown Fortran name mangling: Are you sure the C and Fortran compilers are
> compatible?
>
> Perhaps one is 64 bit and one is 32 bit?
>
> *******************************************************************************
>
> File "./config/configure.py", line 405, in petsc_configure
>
> framework.configure(out = sys.stdout)
>
> File
> "/global/u2/a/apbhalla/softwares/PETSc-BitBucket/PETSc/config/BuildSystem/config/framework.py",
> line 1091, in configure
>
> self.processChildren()
>
> File
> "/global/u2/a/apbhalla/softwares/PETSc-BitBucket/PETSc/config/BuildSystem/config/framework.py",
> line 1080, in processChildren
>
> self.serialEvaluation(self.childGraph)
>
> File
> "/global/u2/a/apbhalla/softwares/PETSc-BitBucket/PETSc/config/BuildSystem/config/framework.py",
> line 1061, in serialEvaluation
>
> child.configure()
>
> File
> "/global/u2/a/apbhalla/softwares/PETSc-BitBucket/PETSc/config/BuildSystem/config/compilers.py",
> line 1458, in configure
>
> self.executeTest(self.checkFortranNameMangling)
>
> File
> "/global/u2/a/apbhalla/softwares/PETSc-BitBucket/PETSc/config/BuildSystem/config/base.py",
> line 126, in executeTest
>
> ret = test(*args,**kargs)
>
> File
> "/global/u2/a/apbhalla/softwares/PETSc-BitBucket/PETSc/config/BuildSystem/config/compilers.py",
> line 675, in checkFortranNameMangling
>
> raise RuntimeError('Unknown Fortran name mangling: Are you sure the C
> and Fortran compilers are compatible?\n Perhaps one is 64 bit and one is
> 32 bit?\n'+mess)
>
>
>
>
>
> I using the following configure options
>
> ./config/configure.py --CC=cc --CXX=CC --FC=ftn --with-default-arch=0
> --PETSC_ARCH=linux-opt --with-debugging=0 --with-c++-support=1
> --with-hypre=1 --download-hypre=1 --COPTFLAGS="-O3" --CXXOPTFLAGS="-O3"
> --FOPTFLAGS="-O3" --with-x=0
>
>
> I have swapped the Prgn-Env-intel with Prgn-Env-gnu.
>
> The compiler commands return the following:
>
> % cc --version
>
> gcc (GCC) 7.1.0 20170502 (Cray Inc.)
>
> Copyright (C) 2017 Free Software Foundation, Inc.
>
> This is free software; see the source for copying conditions. There is NO
>
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
>
> % which cc
>
> /opt/cray/pe/craype/2.5.12/bin/cc
>
>
> % CC --version
>
> g++ (GCC) 7.1.0 20170502 (Cray Inc.)
>
> Copyright (C) 2017 Free Software Foundation, Inc.
>
> This is free software; see the source for copying conditions. There is NO
>
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
>
> % which CC
>
> /opt/cray/pe/craype/2.5.12/bin/CC
>
>
>
> % ftn --version
>
> GNU Fortran (GCC) 7.1.0 20170502 (Cray Inc.)
>
> Copyright (C) 2017 Free Software Foundation, Inc.
>
> This is free software; see the source for copying conditions. There is NO
>
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
>
> % which ftn
>
> /opt/cray/pe/craype/2.5.12/bin/ftn
>
>
>
> Any suggestions?
>
> Thanks,
>
>
>
More information about the petsc-users
mailing list