[FLASH-USERS] Burn and MA28 Fix

[Chris Daley]

Hi James,

I'm sorry that you have run into this error.  I remember having the
exact same error a few months ago.

I'm a bit confused why it has happened again?  When I discovered this
problem I created a python source file at lib/ma28/libinfo.py which is
called by the setup script.  In this file I generate a build script on 
the fly
named build.csh which calls the Makefile with a variable containing
the extra compilation flags (including e.g. 64 bit reals).  The extra flags
come from your Makefile.h (either FFLAGS_DEBUG, FFLAGS_TEST,
FFLAGS_OPT depending on how you setup), and the Makefile is at
/lib/ma28/source/Makefile.

e.g. In my Makefile .h:
FFLAGS_OPT   = -c --o2 --tp4 -CcdRR8

[cdaley at cetus ma28]$ more build.csh
#!/bin/csh
#  Dont forget to make this file executable!

cd source
gmake clean
gmake -f Makefile EXTRA_FFLAGS=" -c --o2 --tp4 -CcdRR8"
cd ..

What does your build.csh look like?

Chris

James Guillochon wrote:
> Hi guys,
>
> So I had been getting singularity errors in the MA28 library when 
> using the Burn unit in Flash 3.1. Then I realized the issue: The 
> Makefile for the MA28 library does not use the same fortran flag 
> variables as the main Makefile.h specifies (FFLAGS_OPT, etc), and was 
> being compiled (by default) without 64-bit arithmetic. I just copied 
> the flags in FFLAGS_OPT from my site-specific Makefile.h (which 
> includes -r8 and -real_size 64) into the MA28 Makefile, and now I get 
> no more errors.
>
> So I think that future releases should alter the MA28 Makefile such 
> that the compile rule for .F90 files includes these flags, either by 
> using the supplied FFLAGS variables or by just appending them to rule 
> directly.
>