Wouldn't it be much simpler if you would use autotools to setup a standard
Code: Select all
./configure; make; make installREQUEST: ./configure; make; make install
Moderators: Global Moderator, Moderator
-
farhi
- Newbie
- Posts: 1
- Joined: Fri Jun 06, 2008 6:20 pm
- License Nr.: 120, upgraded to paw
REQUEST: ./configure; make; make install
Hi dear VASP gods,
Wouldn't it be much simpler if you would use autotools to setup a standard
procedure for installation, checking for available libraries, compilers, etc ... ? I'm pretty sure this would solve most of the installation posts on this Forum !
Wouldn't it be much simpler if you would use autotools to setup a standard
Last edited by farhi on Fri Jun 06, 2008 6:28 pm, edited 1 time in total.
-
sara
REQUEST: ./configure; make; make install
but dear I have great problemes in the installation
Last edited by sara on Mon Jun 09, 2008 5:01 pm, edited 1 time in total.
-
admin
- Administrator
- Posts: 2921
- Joined: Tue Aug 03, 2004 8:18 am
- License Nr.: 458
REQUEST: ./configure; make; make install
most problems arise because the necessary libraries or compilers are not installed at all or installed in a wrong way. This problem cannot be solved by the procedure you suggest, because it is more basic that just compiling the vasp-code. Just finding the correct releases/paths seems to be a minor problem...
Last edited by admin on Mon Jun 09, 2008 5:57 pm, edited 1 time in total.