The ABINIT Users Mailing List ( CLOSED )

[Masayoshi Mikami <mmikami@yk.rim.or.jp>]

Hello, 

The first point you raised:
Please check ~ABINIT/Infos/makefile_macros_help
In your case, you will need a line in your makefile_macros
HOME = (the full path of your home directory)
before the lines
> LIBS= -L$(HOME)/lib/fftw-2.1.5/libs/ibm/lib  -lfftw -lrfftw \
>       -L$(HOME)/lib/LAPACK/lib/ -llapack  -lessl -lm

The second point you raised:
Could you read our documents, e.g. the review paper ?
X. Gonze et al., Compt. Mater. Sci. 25, 478 (2002).
From the Section 3.3. Portability.
"... The large number ofr platforms on which ABINIT has been installed has 
been made possible thanks to the use of cpp directives, coupled with MAKE 
files and/or different scripts. The unique set of ABINIT source files is 
preprocessed on-the-fly at compilation time, and generates machine-dependent 
code. As a result, ABINIT can work under Unix-type OS, as well as under 
Windows and MacOS."

Here, the *_cpp file is that "machine-dependent code". All right ?

Good continuation,
Masayoshi

P.S. Please start your thread by posting, not following a previous e-mail...
And also, please provide more specific subject.
Some of us are thinking of our netiquette list, 
which may be open sooner or later.
Before that, some of you might get interested in "what is netiquette ?"
http://www.hyperdictionary.com/dictionary/netiquette

On Thu, 29 Jul 2004 01:47:41 -0500 (CDT)
Yunkai Zhou <zhou@sp.msi.umn.edu> wrote:

> Hi,
> I am trying to get familiar with abinit.
> But during the lib building process, I already found
> some features of abinit not so appealing.
> (please consider all my criticisms not as offense
> but as my goodwill to wish that abinit will become
> better and better).
> 
> The first is that I don't see (from my brief look at installation
> guide) how to assign other libs to $(LIBS).
> For example, I set the variable
> 
> LIBS= -L$(HOME)/lib/fftw-2.1.5/libs/ibm/lib  -lfftw -lrfftw \
>       -L$(HOME)/lib/LAPACK/lib/ -llapack  -lessl -lm
> 
> But I got error:
> --
> ld: 0706-006 Cannot find or open library file: -l lapack
>         ld:open(): A file or directory in the path name does not exist.
> make: 1254-004 The error code from the last command is 255.
> --
> 
> I think there is not reason to insist users to use the attached
> LAPACK FFT etc (LAPACK v3.0 is available and pretty easy to install),
> newer version of FFTW is available too.  What's more, the user does
> not need to rebuild libs that are already available.  Vender optimized
> libs would possibly be better choices.
> 
> 
> The 2nd is about speed. I found it difficult to understand why you
> have to produce a temp *_ccp.f file, then compile it, then remove it.
> On some remote file systems, this is really slow!! It took several
> hours to compile and build allseq (I am using pretty fast IBM regatta).
> Not because of the compile time is long, but because creating the temp
> files on remote disk is slow. Even after I move abinit to the local
> disk (usually in some /scratch dirs), the temp files creation speed
> improves, but it is still a bit slow to build abinit.
> I have not looked into source files carefully (I guess the _ccp.f
> is to put the included files in the source file?? But cannot compilers
> handle the include directly? Modern compilers are developing so fast).
> 
> Thanks,
> 
> --
> Yunkai Zhou
> 
> 
> 


-- 
----------------------------------------------
Masayoshi Mikami (Yokohama, Japan)
  office:  mmikami.masayoshi@mv.m-kagaku.co.jp
  home:    mmikami@yk.rim.or.jp
  webmail: mikami67@netscape.net
  webmail: mmikami_yk@yahoo.co.jp
(I'm reading/writing e-mail on Linux)
----------------------------------------------