Hi all,
I'm stuck for several days with writing a Makefile with source files
dynamically generated. This problem raises because of a bug in a
compiler when a fortran file uses too many modules and I have to split
it automatically. The original fortran file is dynamically generated too
but wit
Makefile.
Patrick
Le 17/10/2022 à 18:49, Paul Smith a écrit :
On Mon, 2022-10-17 at 18:35 +0200, Patrick Begou wrote:
This file will be splitted in master_1.f90, master_2.f90,
master_3.f90 etc (number of file not known), each of them is a
fortran module and master will be rewritted to use these
Hi all,
I'm stuck for several hours in trying to write a rule for managing
fortran modules. My difficulty is that the Cray compiler requires a
module name written in upper case.
example: if file is "toto_m.f90", it contains a module called "toto_m"
and the module file will be "TOTO_M.mod".
it must be
portable.
Patrick
Le 25/11/2022 à 16:30, Paul Smith a écrit :
On Fri, 2022-11-25 at 15:26 +0100, Patrick Begou wrote:
How can I write a generic rule for building TOTO_M.mod from
toto_m.f90 source and put it in the LIB folder ?
There is no way to do this using "straightforward
Fri, Nov 25, 2022 at 11:33 AM Kaz Kylheku wrote:
On 2022-11-25 06:26, Patrick Begou wrote:
> Hi all,
>
> I'm stuck for several hours in trying to write a rule for
managing fortran modules. My difficulty is that the Cray compiler
requires a module name
