public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: g77 on cygwin64
Date: Wed, 12 Feb 2014 06:00:00 -0000	[thread overview]
Message-ID: <52FB0686.8080403@gmail.com> (raw)
In-Reply-To: <52FAF082.6020805@appstate.edu>



On 12/02/2014 04:54, Scott T. Marshall wrote:
> Hi All,
> First a compliment: I recently went from the old x86 version of cygwin
> to cygwin64. I was pleased to see that many of my perl scripts run about
> twice as fast. Thanks!
>
> My question: Would it be possible to have the old g77 fortran compiler
> as an optional install for cygwin64? I realize that g77 is now
> deprecated by gfortran, but I have a lot of old fortran 77 code that
> does not compile correctly with gfortran. Since I am not a fortran coder
> (I mainly use interpreted languages), I do not have the skills to figure
> out what the issues with gfortran are. It would immensely useful to have
> a cygwin64 g77 as an optional install.
>
> If this is not an option, could anyone maybe point me in the right
> direction as to how to compile g77 myself? I attempted to do so with an
> old g77 from gcc version 3.4.6, but the makefiles do not recognize the
> uname of cygwin64, and I'm not sure of what compiler flags to use, so
> the build always fails.
>
> Any tips/suggestions would be appreciated.
> Cheers,
> -Scott
>

have you tested with -std=legacy ?

'-std=STD'
      Specify the standard to which the program is expected to conform,
      which may be one of 'f95', 'f2003', 'f2008', 'gnu', or 'legacy'.
      The default value for STD is 'gnu', which specifies a superset of
      the Fortran 95 standard that includes all of the extensions
      supported by GNU Fortran, although warnings will be given for
      obsolete extensions not recommended for use in new code.  The
      'legacy' value is equivalent but without the warnings for obsolete
      extensions, and may be useful for old non-standard programs.  The
      'f95', 'f2003' and 'f2008' values specify strict conformance to the
      Fortran 95, Fortran 2003 and Fortran 2008 standards, respectively;
      errors are given for all extensions beyond the relevant language
      standard, and warnings are given for the Fortran 77 features that
      are permitted but obsolescent in later standards.  '-std=f2008ts'
      allows the Fortran 2008 standard including the additions of the
      Technical Specification (TS) 29113 on Further Interoperability of
      Fortran with C.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2014-02-12  5:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-12  4:35 Scott T. Marshall
2014-02-12  6:00 ` Marco Atzeri [this message]
2014-02-12  7:05   ` Scott T. Marshall
2014-02-12  7:24     ` Andrey Repin
2014-02-12  8:00       ` Arjen Markus
2014-02-12 16:04         ` Scott T. Marshall
2014-02-12 17:20           ` Marco Atzeri
2014-02-12 17:59             ` LMH
2014-02-12 19:38               ` Marco Atzeri
2014-02-12 17:36           ` Andrey Repin
2014-02-12 18:07             ` David Conrad
2014-02-12 19:11               ` Richard
2014-02-12 19:59                 ` Marco Atzeri
2014-02-12 21:37               ` Tim Prince
2014-02-12 19:41           ` Achim Gratz
2014-02-12 23:05           ` carolus
2014-02-12 16:16       ` Christopher Faylor
2014-02-12  7:31     ` LMH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52FB0686.8080403@gmail.com \
    --to=marco.atzeri@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).