public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Holcomb, Katherine A (kah3f)" <kah3f@virginia.edu>
To: "emcramer@gmail.com" <emcramer@gmail.com>,
	Elliot Cramer <elliottcramer@bellsouth.net>,
	"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: RE: Fortran compiler
Date: Sun, 24 Apr 2022 13:49:22 +0000	[thread overview]
Message-ID: <MN2PR13MB296092A90A5F8FBF2CDF46E692F99@MN2PR13MB2960.namprd13.prod.outlook.com> (raw)
In-Reply-To: <988059216.388691.1650769067067@mail.yahoo.com>

Hi,

I have an online Fortran course
https://learning.rc.virginia.edu/courses/fortran_introduction/
The section on "Setting Up Your Environment" has instructions for installing gfortran on Windows using MinGW-w64

You generally need some kind of IDE on Windows.  I use one called Geany (free) but there are other options.

-----Original Message-----
From: Fortran <fortran-bounces+kholcomb=virginia.edu@gcc.gnu.org> On Behalf Of emcramer--- via Fortran
Sent: Saturday, April 23, 2022 10:58 PM
To: jvdelisle2@gmail.com; Elliot Cramer <elliottcramer@bellsouth.net>; fortran@gcc.gnu.org
Subject: Re: Fortran compiler

Windows 10

Sent from AT&T Yahoo Mail on Android 
 
  On Sat, Apr 23, 2022 at 10:01 PM, Jerry D<jvdelisle2@gmail.com> wrote:   Elliot,

Let me know what system you want the compiler to run on?

Linux, Windows, PowerPC?

I can guide you through installing on some of these.

Usually we build it from source. However, many linux distributions have packages you can install easily.

Cheers,

Jerry

On 4/23/22 9:31 AM, Elliot Cramer wrote:
> A few years ago I started converting a large old Fortran program which 
> I had running on an IBM 7040 and then on a 360. I have a copy of Lahey 
> Fortran and ran into a compiler bug and gave up on it. How can I 
> download your compiler and get documentation. I don't understand what 
> I've read on the internetThanksElliot
>
> Sent from AT&T Yahoo Mail on Android

  

  reply	other threads:[~2022-04-24 13:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <589966387.343093.1650731463650.ref@mail.yahoo.com>
2022-04-23 16:31 ` Elliot Cramer
2022-04-24  2:00   ` Jerry D
2022-04-24  2:57     ` emcramer
2022-04-24 13:49       ` Holcomb, Katherine A (kah3f) [this message]
2022-04-26  1:57     ` Elliot Cramer
2022-04-26  6:20       ` Arjen Markus
2022-04-26 11:55       ` Holcomb, Katherine A (kah3f)
     [not found]         ` <79cd86c8-44fb-326e-cd0e-a7728b63b708@bellsouth.net>
2022-04-26 14:05           ` Holcomb, Katherine A (kah3f)
2012-10-31 23:48 Fortran Compiler Attaway,Paige G
2012-11-01  1:02 ` Tim Prince
     [not found] <1296477319.26388.ezmlm@gcc.gnu.org>
2011-01-31 19:17 ` fortran compiler David Bourne
  -- strict thread matches above, loose matches on Subject: below --
2011-01-30 17:36 FX
2011-01-30 12:40 Alberto Carramiñana
2011-01-30 13:15 ` Steve Kargl
     [not found]   ` <FD8F47C0-8F7D-4750-969F-95C5C1226D77@inaoep.mx>
2011-01-30 17:08     ` Steve Kargl
     [not found] <bdca99240702200754x7489c3e5tbe82ad4409107631@mail.gmail.com>
2007-02-20 16:03 ` Fortran Compiler Tobias Schlüter
2004-09-02 10:13 Fortran compiler Muhannad
2004-09-02 10:32 ` Tobias Schlüter

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=MN2PR13MB296092A90A5F8FBF2CDF46E692F99@MN2PR13MB2960.namprd13.prod.outlook.com \
    --to=kah3f@virginia.edu \
    --cc=elliottcramer@bellsouth.net \
    --cc=emcramer@gmail.com \
    --cc=fortran@gcc.gnu.org \
    /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).