cannot run
Fortran compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.
make: *** [FoX/.config] Error 1
I don't want it to run compiled programs!
You should :) otherwise you'll never be able to run siesta.
I prefer "make" to do the compiling and leave the running to me. It's doing some
obscure test internally, of which I have no way of knowing what went wrong, and
then concludes that it shouldn't proceed. Did it fail to compile? If so, how can
I see the error message? Did it really try to start an executable compiled with
mpif90? They may need a network that's not present on the compilation machine
(not the case here, but how do I find out what IS the case?).
Now seriously, I am not sure of what the problem might be exactly, but
it basically says that your fortran compiler is not working that well.
What is the compiler you are using? In your output it says intel 9, is
it correct? (If you are not sure, just try mpirun -V ; if it's intell,
it's gonna tell you its build as well.)
The first line is a leftover from the arch.make I started from. It's actually
OpenMPI sing Intel 11.1. I took most of the configuration settings from a
working Makefile I crated for VASP, so the individual components can't be
totally broken. I am obviously making a mistake, but the script is hiding the
relevant information from me!
If it's Iv9, then, have you tried using a newer version instead? Intel v
9, in my experience, has some nasty bugs that would affect the execution
of a few things in siesta-2.0, and they could manifest, perhaps, in the
compilation of the newer version of siesta - never tried it, though. The
run-time errors I had in siesta-2.0 disappeared when I upgraded to 10.1.
You can also try using a safer compiler, which is g95, at the expense of
less efficiency/adrenaline. The nice thing is, if you are using
scalapack and blacs from the cmkl, it's possible that g95 would be able
to link them - it does link the serial mkl libraries, at least.
Switching to g95 (or rather gfortran) just because some script doesn't like the
look of my executables seems a bit counterproductive. I'm sure the problem is
simple, but it will take me hours to debug because somebody decided that it's
too complicated to show me.
Thanks anyway,
Herbert
--
Herbert Fruchtl
Senior Scientific Computing Officer
School of Chemistry, School of Mathematics and Statistics
University of St Andrews
--
The University of St Andrews is a charity registered in Scotland:
No SC013532
