²é¿´: 670  |  »Ø¸´: 5
µ±Ç°Ö÷ÌâÒѾ­´æµµ¡£
µ±Ç°Ö»ÏÔʾÂú×ãÖ¸¶¨Ìõ¼þµÄ»ØÌû£¬µã»÷ÕâÀï²é¿´±¾»°ÌâµÄËùÓлØÌû

huangye2001

ľ³æ (ÕýʽдÊÖ)

[½»Á÷] [ÇóÖú] Çë½Ìabinit 5.4-4µÄ°²×°·½·¨

¸÷λѧ³¤£¬ÇëÎÊabinit 5.4-4ÔÚlinuxÏÂÊÇÈçºÎ°²×°µÄ£¿ÔÚ°²×°Ç°ÐèÒªÏȰ²×°ÄÇЩÈí¼þѽ£¿ÕâЩԤ±¸Èí¼þÒªµ½ÄÇÀïÈ¥ÏÂÔØ£¿×îºÃÊǰѾßÌåµÄ°²×°¹ý³Ì¸æËßÎÒ£¬ÌáǰллÁË£¡×£¸÷λ¹¤×÷Óä¿ì

[ Last edited by huangye2001 on 2008-4-16 at 13:41 ]
»Ø¸´´ËÂ¥
ÒÑÔÄ   »Ø¸´´ËÂ¥   ¹Ø×¢TA ¸øTA·¢ÏûÏ¢ ËÍTAºì»¨ TAµÄ»ØÌû

kanminbad

½ð³æ (СÓÐÃûÆø)

¡ï ¡ï ¡ï
lei0736(½ð±Ò+3,VIP+0):лл
ÎÒÀ´¸øÄã˵һÏ£¬ÎÒ°²×°¹ý5.4.3¡£

Ê×ÏÈÎÒ²»ÖªµÀÄãÓõÄÊÇÄĸölinux£¬½¨ÒéʹÓÃubuntu£¬ÓеÄÔ´ÀïÃæ¾ÍÓÐabinit£¬Ê¹ÓÃÐÂÁ¢µÃºÜÈÝÒ×°²×°£¬µ±È»ÁË£¬²»ÊÇ×îеÄ5.4.4°æ±¾¡£

Èç¹û²»ÊÇubuntu£¬¶øÊDZðµÄlinux£¬ÄǾÍÏà¶ÔÂ鷳Щ¡£¿ÉÒÔÏÈ./configure > log
È»ºó²é¿´logÎļþ£¬¿´ÄÄЩûÓа²×°£¬È»ºóÏàÓ¦µÄ°²×°Éϼ´¿É

Æäʵlinux²Ù×÷ϵͳºÜ¶à£¬ÉÔÓв»Í¬¡£°³Ò²ÊDzËÄñ£¬Ò²²»Ì«¶®£¬Ï£ÍûÓÐËù°ïÖú¡£
5Â¥2008-04-28 21:55:12
ÒÑÔÄ   »Ø¸´´ËÂ¥   ¹Ø×¢TA ¸øTA·¢ÏûÏ¢ ËÍTAºì»¨ TAµÄ»ØÌû
²é¿´È«²¿ 6 ¸ö»Ø´ð

y1ding

Ìú¸Ëľ³æ (ÖøÃûдÊÖ)

¡ï ¡ï ¡ï
suntao1982(½ð±Ò+3,VIP+0):лл£¬»¶Ó­³£À´¼ÆËãÄ£Äâ°æ£¡
2. How to make the executables ?
If you got the binary executable package, you should skip the present section and go to the internal testing section. These executables are presently stored in the ~abinit/opt subdirectory.

We now suppose that you have a F90 compiler and you want to compile the source files.

In most cases, you will have to provide to the 'make' utility some information: the location of the F90 compiler (and sometimes even the C compiler) on your machine, the adequate compiler options, and, if you want to produce the parallel binaries, the location of the MPI library on your machine.
Although the presently implemented building tools should be powerful enough to succeed to make the binaries without you giving such information, it has been seen that on a significant number of platforms, it was better still to give them.

Supposing that you are in the lucky case where the build system is able to find all the information, then the build of ABINITv5 is very simple. Issue :

configure or ./configure (or first create a tmp directory, then cd tmp, then ../configure)
make or ./make (or ./make multi for using several processors on a SMP machine)
(optionally) ./make install
Well, it might also be that only one additional information is needed, in which case something like
configure FC=f95
make
might work. In both cases, let's explain a bit what is done, and the further possibilities.
The 'configure' step produces the set of Makefile files (among other things), taking into account information about your machine and the hostname.ac file. It takes one minute long, or less. The 'make' step compiles everything, according to the Makefile files produced in the prior step. The time to make everything is highly dependent on the compiler and platform. On a 2.8 GHz bi-proc machine (using make multi), the whole compilation is about 4 minutes. On some other platforms, with only one processor, it might be more than one hour.

The executables will be located in the subdirectory ~abinit/src/main, if you have chosen to issue ./configure in the ~abinit directory. If you have issued ./configure in another directory, it will be placed accordingly.

The 'make' command can also be used in many different ways, by mentioning one or more targets. A (partial) list of targets for users can be obtained by typing

make help
Additional targets, for developers, can be obtained by typing
make help_dev
It is possible to compile only one of the executable, just after the configure step by typing


make name_of_the_binary    (where name_of_the_binary can be abinis, abinip, abinitgw, newsp ...)

These are only a tiny fraction of the things that you can realize thanks to 'make'. Moreover, there are also 'Makefile' files in most of the subdirectories of ABINIT, with often their own (partial) list of targets for users (and also sometimes for developers). To obtain these lists, go to the directory, and type
make help
or
make help_dev
Finally,

make install
will install abinit in the /opt/etsf directory (etsf is the abbreviation of European Theoretical Spectroscopy Facility). In the directory ~abinit/doc/config , you will find two important help files, in case you want to go further : build-howto.txt and using-configure.txt .
Let's come back to the case where the build system needs some more information. This information should be stored in a file named hostname.ac , where "hostname" is the result of executing the command "hostname" on your machine, e.g. sleepy.pcpm.ucl.ac.be or dirac ... , and taking the first word of the returned chain of character, e.g. sleepy or dirac ...
There is a template for such a file, located in ~abinit/doc/config . Its name is build-config.ac . Examples of such files, that have been used for testing the package, can be found in ~abinit/doc/config/build-examples . By the way, the known problems observed for these different tests are mentioned in the ~abinit/KNOWN_PROBLEMS file, and the hostname.ac files are correspondingly indicated at the beginning of this file.

The hostname.ac file can be compared to the previously used 'makefile_macros' file (in ABINITv4 and prior). In general, you will notice that much less information is required. The new build system is much more clever than the previous one. The most examples given in the ~abinit/doc/config/build-examples contain about five definitions : F90 and C locations, F90 and C options, MPI library location (or the indication that MPI is not enabled). On the other hand, there are many other possible control flags, needed for advanced use. The activation of additional libraries (NETCDF, NQXC, XMLF90) should cause less problems than in the previous build system.

Your hostname.ac file might be placed in your home directory (this is new compared to the previous build system), in a new directory that you will name ~/.abinit/build . At that location, everytime you install a new version of ABINIT, the needed information will be found by ABINIT, so you do not have to care anymore about this file after the first installation.

On the other hand, if you need to play with several computers, you can place the hostname.ac file directory in the ~abinit directory, where such a hostname.ac file will be also seen by the build system (and preferred over the one located in ~/.abinit/build ) or in your build directory (like ~abinit/tmp). As mentioned above, you might even type at the terminal the definitions contained in the hostname.ac file.

Note the order of precedence for the location of the hostname.ac file (or command-line information), in case more than one possibility is used, (decreasing order of precedence) :

Command line (overcome all other information)
Your build directory (~abinit/tmp)
The ABINIT top directory (~abinit)
~/.abinit/build
/etc/abinit/build
Finally, note that the first generation of a hostname.ac file can be done quite straighforwardly if you can rely on the 'makefile_macros' file that was used previously for your machines (in ABINITv4 or prior). As a first try, simply copy the values for the Fortran 90 compiler, perhaps the options for the libraries, and (eventually) the MPI location. As an example, for the machine sleepy.pcpm.ucl.ac.be, the three following information were given in the makefile_macros file :

FC=/usr/pgi-4.0-2/linux86/bin/pgf90 -Bstatic
FFLAGS_LIBS = -O2
MPI_A=-L/usr/local/mpi-pgi4/lib -lmpichf90 -lpmpich -lmpich -lpmpich
from which the (reformatted) definitions can be set-up, in the hostname.ac file :
FC="/usr/pgi-4.0-2/linux86/bin/pgf90"
with_fortran_optflags="-O2 -Bstatic"
with_mpi_prefix="/usr/local/mpi-pgi4"
All other information from the makefile_macros file are not needed anymore. Compare the file (from version 4.6.5)
~abinit/Machine_dept_files/Intel_P6/makefile_macros.PGI4.0.2static_sleepy
with the new file
~abinit/doc/config/build-examples/i686-pgi4.0_sleepy.ac
As an additional useful trick, note that you might specify e.g. the location of a mpif.h file (e.g. /full_path/mppif.h) using
--with-mpi-fcflags="-I/full_path"

When the hostname.ac file is ready, you have to issue, in the ~abinit directory :

configure or ./configure (or first create a tmp directory, then cd tmp, create a hostname.ac file, then ../configure)
make or ./make (or ./make multi for using several processors on a SMP machine)
(optionally) ./make install
2Â¥2008-04-16 17:08:36
ÒÑÔÄ   »Ø¸´´ËÂ¥   ¹Ø×¢TA ¸øTA·¢ÏûÏ¢ ËÍTAºì»¨ TAµÄ»ØÌû

y1ding

Ìú¸Ëľ³æ (ÖøÃûдÊÖ)

3Â¥2008-04-16 17:08:51
ÒÑÔÄ   »Ø¸´´ËÂ¥   ¹Ø×¢TA ¸øTA·¢ÏûÏ¢ ËÍTAºì»¨ TAµÄ»ØÌû

huangye2001

ľ³æ (ÕýʽдÊÖ)

ллÄúÃǵİïÖú£¡¿ÉÊÇÓÉÓÚ¶ÔlinuxËùÖªÉõÉÙ£¬ÎÒ²»ÖªµÀ¸ÃÈçºÎ°²×°fortran90ÇÒÒ²²»ÖªµÀÔÚÄÇÏÂÔØµ½¸ÃÈí¼þ£¡ÇëÇó°ïÖú¡£Â鷳ѧ³¤ÁË¡£
4Â¥2008-04-17 09:59:19
ÒÑÔÄ   »Ø¸´´ËÂ¥   ¹Ø×¢TA ¸øTA·¢ÏûÏ¢ ËÍTAºì»¨ TAµÄ»ØÌû
×î¾ßÈËÆøÈÈÌûÍÆ¼ö [²é¿´È«²¿] ×÷Õß »Ø/¿´ ×îºó·¢±í
[˶²©¼ÒÔ°] ÊÛSCIÒ»ÇøÎÄÕ£¬ÎÒ:8 O5 51O 54,¿ÆÄ¿ÆëÈ«,¿É+¼± +3 8rmuugja8q 2026-02-22 7/350 2026-02-23 09:44 by w4l55oybr1
[¿¼ÑÐ] ÊÛSCIÒ»ÇøÎÄÕ£¬ÎÒ:8 O5 51O 54,¿ÆÄ¿ÆëÈ«,¿É+¼± +3 khieu8v8m0 2026-02-22 8/400 2026-02-23 09:35 by w4l55oybr1
[ÂÛÎÄͶ¸å] ÊÛSCIÒ»ÇøÎÄÕ£¬ÎÒ:8 O5 51O 54,¿ÆÄ¿ÆëÈ«,¿É+¼± +4 khieu8v8m0 2026-02-22 8/400 2026-02-23 09:29 by w4l55oybr1
[¿¼ÑÐ] ÊÛSCIÒ»ÇøÎÄÕ£¬ÎÒ:8 O5 51O 54,¿ÆÄ¿ÆëÈ«,¿É+¼± +5 usprnugpzw 2026-02-21 11/550 2026-02-23 09:24 by w4l55oybr1
[½Ìʦ֮¼Ò] ΪʲôÖйú´óѧ¹¤¿Æ½ÌÊÚÃÇË®ÁËÄÇô¶àËùνµÄ¶¥»á¶¥¿¯£¬µ«»¹ÊÇ×ö²»³öÓîÊ÷»úÆ÷ÈË£¿ +5 »¶ÀÖËÌÒ¶Ýè 2026-02-21 8/400 2026-02-23 09:19 by »¶ÀÖËÌÒ¶Ýè
[ÂÛÎÄͶ¸å] ÊÛSCIÒ»ÇøÎÄÕ£¬ÎÒ:8 O5 51O 54,¿ÆÄ¿ÆëÈ«,¿É+¼± +3 w89i99eaeh 2026-02-22 5/250 2026-02-23 08:04 by w4l55oybr1
[²©ºóÖ®¼Ò] ÊÛSCIÒ»ÇøÎÄÕ£¬ÎÒ:8 O5 51O 54,¿ÆÄ¿ÆëÈ«,¿É+¼± +4 khieu8v8m0 2026-02-22 6/300 2026-02-23 07:59 by w4l55oybr1
[²©ºóÖ®¼Ò] ÊÛSCIÒ»ÇøÎÄÕ£¬ÎÒ:8 O5 51O 54,¿ÆÄ¿ÆëÈ«,¿É+¼± +6 3dfhjxgsh7 2026-02-22 9/450 2026-02-23 07:49 by w4l55oybr1
[¹«Åɳö¹ú] ÊÛSCIÒ»ÇøÎÄÕ£¬ÎÒ:8 O5 51O 54,¿ÆÄ¿ÆëÈ«,¿É+¼± +3 khieu8v8m0 2026-02-22 5/250 2026-02-23 06:29 by w4l55oybr1
[˶²©¼ÒÔ°] ÊÛSCIÒ»ÇøÎÄÕ£¬ÎÒ:8 O5 51O 54,¿ÆÄ¿ÆëÈ«,¿É+¼± +4 khieu8v8m0 2026-02-22 8/400 2026-02-23 06:24 by w4l55oybr1
[¿¼²©] ÊÛSCIÒ»ÇøÎÄÕ£¬ÎÒ:8 O5 51O 54,¿ÆÄ¿ÆëÈ«,¿É+¼± +5 3dfhjxgsh7 2026-02-22 6/300 2026-02-23 02:04 by 5jlh3qtdvx
[½Ìʦ֮¼Ò] °æÃæ·Ñ¸Ã½»Âð +7 Æ»¹ûÔÚÄÄÀï 2026-02-22 8/400 2026-02-22 22:37 by otani
[»ù½ðÉêÇë] ÃæÉÏ¿ÉÒÔ³¬¹ý30Ò³°É£¿ +4 °¢À­¹±aragon 2026-02-22 4/200 2026-02-22 21:22 by ɽÎ÷Ðü¿ÕË¿ÕÐüÎ
[ÂÛÎÄͶ¸å] ÊÛSCIÒ»ÇøÎÄÕ£¬ÎÒ:8 O5 51O 54,¿ÆÄ¿ÆëÈ«,¿É+¼± +4 usprnugpzw 2026-02-21 6/300 2026-02-22 19:48 by w89i99eaeh
[¿¼ÑÐ] ÊÛSCIÒ»ÇøÎÄÕ£¬ÎÒ:8 O5 51O 54,¿ÆÄ¿ÆëÈ«,¿É+¼± +3 3dfhjxgsh7 2026-02-22 4/200 2026-02-22 16:52 by khieu8v8m0
[ÕÒ¹¤×÷] ÊÛSCIÒ»ÇøÎÄÕ£¬ÎÒ:8 O5 51O 54,¿ÆÄ¿ÆëÈ«,¿É+¼± +3 usprnugpzw 2026-02-22 3/150 2026-02-22 16:37 by khieu8v8m0
[»ù½ðÉêÇë] ¡°ÈËÎÄÉç¿Æ¶øÂÛ£¬Ðí¶àѧÊõÑо¿»¹Ã»ÓдﵽÃñ¹úʱÆÚµÄˮƽ¡± +4 ËÕ¶«ÆÂ¶þÊÀ 2026-02-18 5/250 2026-02-22 16:07 by liangep1573
[»ù½ðÉêÇë] ʲôÊÇÈËÒ»Éú×îÖØÒªµÄ£¿ +4 ˲ϢÓîÖæ 2026-02-21 4/200 2026-02-22 11:44 by huagongfeihu
[»ù½ðÉêÇë] ½ñÄê´ºÍíÓм¸¸ö½ÚÄ¿ºÜ²»´í£¬µãÔÞ£¡ +11 ˲ϢÓîÖæ 2026-02-16 12/600 2026-02-21 21:14 by lq493392203
[»ù½ðÉêÇë] ÌåÖÆÄÚ³¤±²ËµÌåÖÆÄÚ¾ø´ó²¿·ÖÒ»±²×ÓÔڵײ㣬ÈçͬÄãÃÇÒ»Ñù´ó²¿·ÖÆÕͨ½ÌʦæÇÒÊÕÈëµÍ +9 ˲ϢÓîÖæ 2026-02-20 12/600 2026-02-21 10:39 by »¶ÀÖËÌÒ¶Ýè
ÐÅÏ¢Ìáʾ
ÇëÌî´¦ÀíÒâ¼û