On 11/24/2016 03:34 AM, seyedali88 via deal.II User Group wrote:
This problem is giving me a headache. PETSC is one of the buggiest libraries
ever...
If I don't touch anything, the compiler is detected as mpicc (I assume it is
some wrapper based on gcc compiler?) and PETSC compiles fine.
The problem though is that I think mpicc is wrong since I use mpiicc from
Intel for deal.II compilation. Now that is why I try to tell PETSC the
following to do:
export PETSC_DIR=/path/petsc-3.7.4
export PETSC_ARCH=intel_mpi
./config/configure.py \
--with-cc=/opt/intel/compilers_and_libraries_2016.3.210/linux/mpi/intel64/bin/mpiicc
\
--with-cxx=/opt/intel/compilers_and_libraries_2016.3.210/linux/mpi/intel64/bin/mpiicpc
\
--with-fc=/opt/intel/compilers_and_libraries_2016.3.210/linux/mpi/intel64/bin/mpiifort
\
--with-shared-libraries=0 \
--known-mpi-shared-libraries=1 \
--with-x=0 --download-hypre=1 \
--with-debugging=1 \
--with-c++-support=1 \
--with-c-support=1 \
--with-python \
--with-pic=fPIC\
--LIBS='-ldl -lstdc++'\
But I receive this error message:
===============================================================================
Configuring PETSc to compile on your system
===============================================================================
TESTING: checkCLibraries from
config.compilers(config/BuildSystem/config/compilers.py:168)
*******************************************************************************
UNABLE to EXECUTE BINARIES for ./configure
-------------------------------------------------------------------------------
Cannot run executables created with FC. If this machine uses a batch system
to submit jobs you will need to configure using ./configure with the
additional option --with-batch.
Otherwise there is problem with the compilers. Can you compile and run code
with your compiler
'/opt/intel/compilers_and_libraries_2016.3.210/linux/mpi/intel64/bin/mpiifort'?
See http://www.mcs.anl.gov/petsc/documentation/faq.html#libimf
*******************************************************************************
I think without mpiicc the step-40 in deal.II will not work properly. I also
tried to use MPICH and OPENMPI where both didnt'work since PETSC cannot detect
the compilers correctly altthough I set PATH and LD_LIBRARY_PATH...
The PETSC version I am now using is 3.7.4 since I want to use the latest
version. It should work and I hope to find the solution with your help.
It is correct that you will not be happy with the result if you use different
MPI installations for PETSc and deal.II. Lots of strange error messages will
happen downstream.
What you ought to do is either:
1/ Figure out why PETSc believes that the fortran compiler specified with FC
does not work. You could, for example, look into the files that ./configure.py
creates and into which it posts the error messages it gets for the tests it
runs. There should also be the error message for the test that makes it think
that the fortran compiler doesn't work.
2/ Disable Fortran. PETSc is written in C. You should be able to just disable
those parts for which it wants to use Fortran. I'm sure there's a configure
switch for that. (--with-fortran-support=0 ?)
Best
W.
--
------------------------------------------------------------------------
Wolfgang Bangerth email: [email protected]
www: http://www.math.colostate.edu/~bangerth/
--
The deal.II project is located at http://www.dealii.org/
For mailing list/forum options, see
https://groups.google.com/d/forum/dealii?hl=en
---
You received this message because you are subscribed to the Google Groups "deal.II User Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
