Skip to Content.
Sympa Menu

forum - Re: [abinit-forum] gfortran-compiled ABINIT yields two failed tests. Is this a problem?

forum@abinit.org

Subject: The ABINIT Users Mailing List ( CLOSED )

List archive

Re: [abinit-forum] gfortran-compiled ABINIT yields two failed tests. Is this a problem?


Chronological Thread 
  • From: "Anglade Pierre-Matthieu" <anglade@gmail.com>
  • To: forum@abinit.org
  • Subject: Re: [abinit-forum] gfortran-compiled ABINIT yields two failed tests. Is this a problem?
  • Date: Tue, 12 Feb 2008 16:37:57 +0100
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=IoWRUfGEAzyHOwPJ3SB17zdCYSPfoAq5wXDdsNVU5bnjfPZV3xVTXoe0mUO6W2nCp4rrLxgFHnuW+XM7W/hM/Betk1s1loRSZ2tX9sR+sMig+guVon23t7tkKongM7Ce+akayRpe1Zre0R5XMNnZFwvdQDUbg/0GcYQpXGeuErk=

> I wonder if that affects things.

It is at least not impossible because the developpers have never tested this couple.

I tend to always use synchronous version of the gfortran frontend and gcc backend. This avoid you the problem of being the only one to suffer from a bug because of a very exotic front/back-end couple.  (Noticed that gfortran is simply a fortran frontend to the gnu compiler collection ?). When such a reliable couple is not available on the system I tend to install it for my self. It's quite easy  (config --prefix=...; make; make install (at the configure step check that gfortran is going to be built). Afterwards you just have to build static binaries in order to avoid any runtime surprise.

Best,

PMA

On Feb 12, 2008 2:19 PM, J. J. Ramsey <jjr19@uakron.edu> wrote:



----- Original Message ----

From: Anglade Pierre-Matthieu <anglade@gmail.com>

To: forum@abinit.org

Sent: Tuesday, February 12, 2008 3:14:41 AM

Subject: Re: [abinit-forum] gfortran-compiled ABINIT yields two failed tests. Is this a problem?



> Here with gfortran 4.2.2 everything works fine on a intel core2 - FC 8/EMT64. I guess this may be due either to:

 > 1) over optimization (have you tryed something special ?)

No. I did not specify any optimization options myself.

> 2) also many version of gfortran coming with gcc 4.2 and 4.3 were not quite "perfect".

That's what I was afraid of.

> And since we don't know exactly the date of the
> release (they are release aren' they ?) you use it may be the root of your problem.

As far as I know, the gfortran I used on Linux is a release (version 4.2.1), but the one I use on OS X is from http://gcc.gnu.org/wiki/GFortranBinariesMacOS, which is not.

> The not so mature version of gfortran were all conflicting with Abinit PAW so my best guess is that you need a newer stable version of
> gcc. But its not quite sure.

I noticed that you wrote "gcc" and not "gfortran" here. Now on my Linux system at work, the version of *gcc* is 4.1.3, which is not the same as the version of gfortran. Actually, to my surprise, gcc itself is a 20070929 prerelease (which I didn't notice until just now). On OS X, the Apple Developer Tools, version 2.5, still use a gcc version of 4.0.x. (I forget the exact version.) I wonder if that affects things.




     ____________________________________________________________________________________
Looking for last minute shopping deals?
Find them fast with Yahoo! Search.  http://tools.search.yahoo.com/newsearch/category.php?category=shopping



--
Pierre-Matthieu Anglade



Archive powered by MHonArc 2.6.16.

Top of Page