[GRASSLIST:4144] Re: make.rules variables

andres javier garcia garcia andresjavier.garcia at wanadoo.es
Wed Jul 24 09:49:45 EDT 2002


Thanks Glynn
I've added, the compiler option, FC = g77, by hand, to 
src/CMD/head/head.<arch>, and now it goes all right.

Javier Garcia



---------------------------
El Lun 22 Jul 2002 23:35, andres javier garcia garcia wrote:
> > I've compiled an aditional module in a computer with no problem. After
> > that, I've tried to do the same in other computer but the process fails.
> > I've realized that in the make.rules files thre is the following: FC =
> > While in the computer in which the compiling has gone right, this same
> > variable is
> > FC = g77
> > I've tried to add this by hand (and several other things), but, when I
> > compile, the variable is erasen again.
> > I've checked that the fortran compiler is correctly installed and works.
> > So, the only thing that I can imagine is that these variables are
> > originally read in other part.
> > Am I right?
> > Please, help. How can I solve this?
>
> The "make.rules" files are automatically generated from the
> corresponding Gmakefile and the files in src/CMD, specifically
> src/CMD/head/head.<arch>.
>
> The configure script generates src/CMD/head/head, which is renamed to
> src/CMD/head/head.<arch> at the start of the build process.
>
> If the definition of FC is empty, then the configure script didn't
> detect the fortran compiler; it checks for a program called g77 or f77
> in the path.



More information about the grass-user mailing list