This is a common case with the intel compilers. :( Sadly there is a bug (loooong lasting) which happens when you compile atom.F with high optimization levels. You need to add this to your arch.make file: atom.o: atom.F $(FC) -c -O1 $(INCFLAGS) $(FPPFLAGS) $
(see e.g. in the Obj/intel.make file for an example) which forces the compilation of atom.o with lower optimization levels. We have tried to narrow it down to no avail. However, we have not seen this with gfortran, even with extremely high optimzation levels. 2017-04-04 21:36 GMT+02:00 I. Camps <[email protected]>: > Hello, > > I successfully compile SIESTa with the set Intel Fortran Compiler/Intel > MPI/Intel MKL > ifort: Intel(R) Fortran Intel(R) 64 Compiler XE for applications running > on Intel(R) 64, Version 15.0.1.133 Build 20141023 > MPI: Intel(R) MPI Library for Linux* OS, Version 2017 Update 1 Build > 20161016 (id: 16418) > MKL: 11.2.1 > > My arch.make file is attached. > > When running SIESTA with the silicon FDF (attached) I got the message: > > ################ > forrtl: severe (174): SIGSEGV, segmentation fault occurred > Image PC Routine Line Source > siesta 0000000001A94261 Unknown Unknown Unknown > siesta 0000000001A929B7 Unknown Unknown Unknown > siesta 0000000001A43464 Unknown Unknown Unknown > siesta 0000000001A43276 Unknown Unknown Unknown > siesta 00000000019F339F Unknown Unknown Unknown > siesta 00000000019F993D Unknown Unknown Unknown > libpthread.so.0 00002B9436D60B00 Unknown Unknown Unknown > siesta 0000000001F25615 Unknown Unknown Unknown > > Stack trace terminated abnormally. > ################ > > This is driving me crazy...so, any help will be very appreciated. > > []'s, > > Camps > -- Kind regards Nick
