Marcos is right. It seems like at the beginning something is being configured on the FoX directory, but as long as you first copy your own arch.make that used to work in previous versions you are fine (are you compiling SIESTA for the very first time?) .
I compiled 3.0b with my arch.make from a previous version. The only problem that arose at some point during compilation was in trying to get the location of some mod files from the FoX directory. For that, I just passed the include directoy location (~/ siesta-3.0-b/Obj/FoX/objs/finclude in my case) on my fortran compiler line: FC=ifort -lmpi -I/u/ac/sbl3/siesta-3.0-b/Obj/FoX/objs/finclude That did it for me. With best regards, -Salvador. ----- Original Message ----- From: "Marcos Veríssimo Alves" <marcos.verissimo.al...@gmail.com> To: siesta-l@uam.es Sent: Saturday, December 12, 2009 12:58:42 PM GMT -05:00 US/Canada Eastern Subject: Re: [SIESTA-L] parallel compilation of 3.0b No. The configure of the modules is "harmless" because it uses the same options as arch.make. If you have an arch.make that works, just type "make", sit back, relax and be happy afterwards ;) On Sat, Dec 12, 2009 at 6:53 PM, Herbert Fruchtl < herbert.fruc...@st-andrews.ac.uk > wrote: The problem is that even if I supply my own arch.make in Obj, "make" will start the configure script from other directories (FoX, but I'm not sure if this is the only one). Do I have to copy my arch.make to all subdirectories of Src? Herbert Quoting Marcos Veríssimo Alves < marcos.verissimo.al...@gmail.com >: > Yes, there is... Just skip the "configure" part, use an arch.make supplied > by you and type "make". It will run a few configure's for the modules of > siesta, which them selves have make files, and start building everything. If > you are too lost about arch.make's, there are plenty of them flying around > on the list archives and of course, on the Src/Sys directory, with many > flavors of compilers and math libraries - but you will most certainly have > to adjust: > > 1) the paths for the libraries (especially blacs and scalapack, which have > to be compiled individually) > 2) the paths for the mpi stuff, if your system has some particular/weird > configuration. > > Now I have realized one thing... are you trying to customize an arch.make > and *after* customizing it typing ../../Src/configure ? I've never done it > myself but I'd guess configure would overwrite whatever you put in the > arch.make with its own guesses, hence no matter what you put in configure > would generate complaints. > > Cheers, > > Marcos > > On Sat, Dec 12, 2009 at 1:31 AM, Herbert Fruchtl < > herbert.fruc...@st-andrews.ac.uk > wrote: > > > Is there a way to compile 3.0b without it trying (and usually failing) to > > determine all the compiler flags by itself? No matter what I put into > > arch.make, it will complain that it cannot determine how to create an > > executable, or run compiled programs (presumably because they need > > mpirun...) > > > > Herbert > > > > > > ------------------------------------------------------------------ > > University of St Andrews Webmail: https://webmail.st-andrews.ac.uk > > > > > -- Herbert Fruchtl EaStCHEM Fellow School of Chemistry University of St Andrews ------------------------------------------------------------------ University of St Andrews Webmail: https://webmail.st-andrews.ac.uk -- Salvador Barraza-Lopez Postdoctoral Fellow School of Physics The Georgia Institute of Technology Office N205 837 State Street Atlanta, Georgia 30332-0430 U.S.A Tel: (404) 894-0892 Fax: (404) 894-9958
