Re: [SIESTA-L] How do I compile with MPI but without shared objectslinkingat runtime?

Thanks Daniel but the issue is not moving the links. The issue is that we build static binaries on the supercomputer so no *.so libraries are available. The tests at configure time are happy with *.a but at run time, according to strace, mmap is searching for libmpich.so. It is happy with libbl

Re: [SIESTA-L] How do I compile with MPI but without shared objectslinking at runtime?

Hello, Ray Sheppard wrote: Hi folks, I am new here. I am trying to compile Siesta 2.0 with MPI on a LINUX PowerPC and MPICH-1.2.7. It configures and runs its tests against libmpich.a and builds. I have added --disable-shared to my configure script. Everything looks fine until runtime. I

[SIESTA-L] How do I compile with MPI but without shared objects linking at runtime?

Hi folks, I am new here. I am trying to compile Siesta 2.0 with MPI on a LINUX PowerPC and MPICH-1.2.7. It configures and runs its tests against libmpich.a and builds. I have added --disable-shared to my configure script. Everything looks fine until runtime. I then get the error: siesta-2.

Re: [SIESTA-L] Compile problem : redeclared MPI data types

Hello Javier, Thanks for your suggestion. Yes, this does solve the compile problem. But when the build process gets to the final step, the linker still complains about unexpected references (see below). This problem must not be limited to the mpi.F module but could be anywhere. Is there a f

Re: [SIESTA-L] Compile problem : redeclared MPI data types

Dear Scott: Edit the mpi.F file in the Src/MPI subdirectory, and include the "USE MPI_INCLUDE, " inside the two blocks of the preprocessor. The final lines should look like: #ifdef OLD_CRAY USE MPI__INCLUDE , & DAT_single => MPI_real, & & DAT_2single => MPI_2real, & & DAT_double => MPI_real, & &