Here is one way to check.
- check make.log for the build - it might have something like:
-
Using system modules:
Using mpi.h: # 1 "/home/balay/soft/mpich-4.0.1/include/mpi.h" 1
-
- now check your application build
Perhaps you need to attach your configure.log
--Junchao Zhang
On Fri, Oct 11, 2024 at 5:14 PM Daniel Pino Munoz <
daniel.pino_mu...@mines-paristech.fr> wrote:
> I did that too, and I am using the same compiler.
>
> In fact I also checked the compilation of my code by setting VERBOSE=1 and
> loo
I did that too, and I am using the same compiler.
In fact I also checked the compilation of my code by setting VERBOSE=1
and looking at the compilation command. It is indeed the same
compiler... It's pretty odd...
Thanks anyway,
D.
On 12/10/2024 00:04, Junchao Zhang wrote:
Check they are
Check they are the same MPI wrappers(if you use them), for example with
"which mpicc" or "make V=1" to compare the exact executable path
--Junchao Zhang
On Fri, Oct 11, 2024 at 4:10 PM Daniel Pino Munoz <
daniel.pino_mu...@mines-paristech.fr> wrote:
> Dear all,
>
> I am currently trying to comp
Dear all,
I am currently trying to compile my code but the compilation fails with
the following error:
error "PETSc was configured with OpenMPI but now appears to be compiling
using a non-OpenMPI mpi.h
I have obviously checked and I am compiling my sources using the same
compiler used to c
PETSc users,
I have been developing an open-source framework called the VnV Toolkit that
helps developers build graphical user interfaces around scientific
applications. Like most documentation generators, the toolkit uses
comments/markup defined in your codebase to generate customized graphical
i
