Re: Praise for Gfortran (finally)

In article
<06fe625c-6212-4723-b31c-fa57b8fa8c69@xxxxxxxxxxxxxxxxxxxxxxxxxxx>,
"tholen@xxxxxxxxxxxx" <tholen@xxxxxxxxxxxxxx> writes:

I think the typical way one gets deeply involved with gfortran
development is as follows:

I'm interested in seeing gfortran ported to another operating
system. I'm assuming that gfortran itself is written in C or
some variant of C, which means a prerequisite is having a C
compiler for that operating system, but as far as I know, the
available version of the gnu C compiler is too old. Perhaps
someone can list the steps necessary to port gfortran to
another operating system.

Shouldn't porting it be trivial? That is, just compile and go? Or is
not everything implemented in the source code of the compiler, but
instead makes use of system calls etc?

.

Relevant Pages

  • Re: Praise for Gfortran (finally)
    ... I'm interested in seeing gfortran ported to another operating ... available version of the gnu C compiler is too old. ... "gcc" works, but it is too old to compile the current GCC. ...
    (comp.lang.fortran)
  • Re: Praise for Gfortran (finally)
    ... I'm interested in seeing gfortran ported to another operating ... some variant of C, which means a prerequisite is having a C ... available version of the gnu C compiler is too old. ...
    (comp.lang.fortran)
  • Re: No input files
    ... gfortran is a compiler that makes object code (or even ... an executable) for a given input file (or multiple input files). ... where test.f90 is the file containing your source code, ...
    (comp.lang.fortran)
  • Re: gfortran and MOD files
    ... the output of the compiler for a module is _not_ for ... for gfortran but the compiler does have to have a way to know where the ... Certainly the Standard does not require that source code ... I see that GFORTRAN does _not_ use any other environment variables ...
    (comp.lang.fortran)
  • Re: gfortran and MOD files
    ... the output of the compiler for a module is _not_ for consumption of anything except by the compiler when it finds a USE for that particular module in another piece of code. ... I would, instead, expect that if you check the documentation you'll find there's an environment variable used that you've not gotten set in your installation or that you're somehow not putting the output of the compiler when compiling the modules into the default location expected by gfortran. ... Certainly the Standard does not require that source code have an INCLUDE for the module to be found and certainly no compiler will like an attempt to actually INCLUDE the .mod file itself in the source code. ... I see that GFORTRAN does _not_ use any other environment variables ...
    (comp.lang.fortran)