The ABINIT Users Mailing List ( CLOSED )

[Alain Jacques <ajs.jacques@gmail.com>]

Dear Aaron,

My intention was to explain that most of the tools for a "post install" test procedure are present but not yet adapted - it is a development in progress, still unfinished.
It is a very bad idea to sudo ... somehow traces of my own computer paths has leaked in the distribution (that's the reason of the /var/jacques path); sudoing will probably allow those scripts to write in places you don't expect and the tests won't probably work as designed.

So - to a certain extend - you have to trust me. I have produced those binaries on an Intel MacPro OSX 10.5.8 with an home made gcc/gfortran-4.3.4. They are optimized for "nocona" Intel architecture i.e. should run fine on Core2 and Xeon Intel Macs. FYI, these are 32bit binaries and a nasty bug has been discovered since I posted the binary distribution. My intention is to redo it with the 5.8.4p - but I'm a bit swamped for the moment
Of course you can run the tests manually and compare the output with the corresponding /Refs/.. reference output (there is a perl script fldiff.pl for this that should work). Or try to reproduce the tutorial samples.

Now if you still have you own compilation attempts source directories of abinit 5.8.4 (and assuming that you have passed the configure and make steps up to the end i.e. the makefile are written) the following hack may work - but it is quite a dirty one. It consists of placing my binaries at the right place in the build tree. Copy the content of the binary distribution abinit-5.8.4/bin directory to the source distribution src/98_main/ (i.e. replace the src/98_main/abinis ... files with my own); copy the binary distribution abinit-5.8.4/lib directory content to the source distribution src/lib/ (not in libs, you'll have to create that one - i.e. produce the src/lib/libgcc*.dylib and src/lib/libgfortran*.dylib files). Check with an otool -L abinis that the executable find all its dependencies. Change to the distribution source src/../tests directory ; try a make ... you should receive back all the tests options, try a "make tests_min" or a "make test_acc". No guarantee whatsoever. But please report your experience.

Alain

... and follow Yann advices :-)



Aaron S. Wolf wrote:

4d11446f0911101036ifd13402v7c0f00437385e3c1@mail.gmail.com" type="cite">Hi Alain-
    I tried to run run-basic-tests.sh after using chmod +x, but it didn't work. It said that I didn't have permissions:
Scripts/run-basic-tests.sh . 1
mkdir: cannot create directory `/var/jacques': Permission denied
I wasn't sure what the script was doing so I decided not to call sudo on it to make it go through. Is using sudo a good idea? Is it possible to run the tests at all once the binaries are created, or must I just trust that everything is working as it should? (I am a little worried about just trusting the output, since I don't have enough familiarity to be sure the code is running correctly without the unit tests provided with the distribution. I can only verify that it runs at all...). Thanks again for all your help!

Best,
Aaron Wolf

On Tue, Nov 10, 2009 at 6:53 AM, Alain Jacques <ajs.jacques@gmail.com> wrote:

Hello Aaron,

I am afraid you cannot run the full test suite again after installing the binaries. The test routines - makefiles, perl - are dependent on the structure of the sources and build directories and are designed to be called from a makefile after compiling the code - . Most of the information is there - look at the scripts run-basic-tests.pl and run-standard-tests.pl.

Kind regards,

Alain

Aaron S. Wolf wrote:

Hi Alain-
   Thanks for those binaries. I don't need to make them myself (at least not right now). I was wondering how to run the tests, since all of the make files are missing, so I can't just use make test1 etc. Thanks for everyones help!
-aaron wolf

On Sat, Nov 7, 2009 at 2:46 AM, Alain Jacques <ajs.jacques@gmail.com> wrote:

Hello Aaron,

First of al, if you don't want to break your head, may I suggest you to
download my OSX binaries from
http://www.etsf.eu/resources/software/etsf_software_repository
They include all the plugins, they are optimized and pass all the tests.

If you insist to do it yourself ... I am a bit lost; I don't know if you
have produced working binaries. What kind of fortran compiler do you use
(Intel, gfortran from Fink or Macport)?  Can you show your configure
options? Can you provide the output of an "otool -L abinis" and "otool
-L abinip"?

...