From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: Alberto Carrami?ana <alberto@inaoep.mx>
Cc: fortran@gcc.gnu.org
Subject: Re: fortran compiler
Date: Sun, 30 Jan 2011 13:15:00 -0000 [thread overview]
Message-ID: <20110130000347.GA86024@troutmask.apl.washington.edu> (raw)
In-Reply-To: <5F951FAB-ADF6-40D0-B18C-3718148B6A7C@inaoep.mx>
On Sat, Jan 29, 2011 at 05:50:02PM -0600, Alberto Carrami?ana wrote:
>
> I just got a new mac and installed the files from my older, now defunct, mac.
> g77 is not working and I do need a fortran compiler for simple use. I write
> simple fortran programs (100 to 1000 lines) for own calculations.
>
> I hope you can help me.
>
>
g77 is dead.
Go to the gfortran wiki, which google can help you find.
Start reading.
--
Steve
next prev parent reply other threads:[~2011-01-30 0:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-30 12:40 Alberto Carramiñana
2011-01-30 13:15 ` Steve Kargl [this message]
[not found] ` <FD8F47C0-8F7D-4750-969F-95C5C1226D77@inaoep.mx>
2011-01-30 17:08 ` Steve Kargl
[not found] <589966387.343093.1650731463650.ref@mail.yahoo.com>
2022-04-23 16:31 ` Fortran compiler Elliot Cramer
2022-04-24 2:00 ` Jerry D
2022-04-24 2:57 ` emcramer
2022-04-24 13:49 ` Holcomb, Katherine A (kah3f)
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)
-- strict thread matches above, loose matches on Subject: below --
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
2011-01-30 17:36 FX
[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=20110130000347.GA86024@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=alberto@inaoep.mx \
--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).