Elmer Discussion Forum

ahmed@debian:~$ cd elmer ahmed@debian:~/elmer$ ./a.out Loads fine ahmed@debian:~/elmer$ please note that the elmer folder is a work folder where I have copied the samples and tutorials, the Elmer programme itself is saved in its standard location. Any clues or hints are highly appreciated Based on ...

Hi,

Could you please try unlimiting the stack size with "ulimit -s unlimited" before launching ElmerGUI?

Does your model complete with the serial solver?

Ok. Could you please run the following small diagnostics utility? Compile and run it as "g++ test.cpp -ldl && ./a.out" #include <iostream> #include <dlfcn.h> int main() { void *h; if(!(h = dlopen("libtet.so", RTLD_LAZY))) { std::cerr << dlerror() << std::endl; return 0; }...

Are you able to run simple MPI programs with your setup?

Check also the -envall switch from mpich user guide.

Are you using tetgen 1.4.2?

The new version 1.4.3 from september 2009 has introduced some changes, which make it incompatible with the current version of ElmerGUI.

The difference between trunk and release is in the ISO_VARYING_STRING module. This module has caused some problems with older compilers like gfortran <= 4.1.

Unfortunately I cannot check your issue, since I do not have access to pathscale 2.2. All I can say it compiles with 2.5, 3.0, 3.1 and 3.2.

What says "mpif90 -show"? Does it compile MPI sample programs?

You might also want to manually inspect the dependencies of your mpi lib by typing "ldd libmpich.so".

Finally, try adding the switch "--with-mpi-dir=/path/to/my/mpi" to the configuration script.

One more thing. Have you checked whether your mpich installation provides MPI-specific wrappers for your compilers? Usually these wrappers are called mpicc, mpic++, mpif90, or something similar. It might be a good idea to use these instead of the plain compiler commands, they should automatically se...

Hi,

If you want to pass a specific library path to the linker, you can use the LDFLAGS variable, e.g. export LDFLAGS=-L/some/path

LD_LIBRARY_PATH is related to runtime loading of shared libraries.

Ok. /opt/mpich2/lib/libmpich.a(allreduce.o): In function `MPIR_Allreduce_inter': allreduce.c:(.text+0x1c7): undefined reference to `pthread_getspecific' It seems that the linker is unable to find `pthread_getspecific' and other functions related to pthreads. So, I'd try adding -lpthread to LIBS befo...