From: Steve Kargl <sgk@troutmask.apl.washington.edu>
To: "Brian T. Brunner" <brian.t.brunner@gai-tronics.com>
Cc: fortran@gcc.gnu.org, gcc-help@gcc.gnu.org
Subject: Re: F77 code under gcc
Date: Fri, 04 Nov 2005 20:04:00 -0000 [thread overview]
Message-ID: <20051104200359.GB56800@troutmask.apl.washington.edu> (raw)
In-Reply-To: <s36b4bf1.052@CRPSPKWANW02-IA.hubbell.com>
On Fri, Nov 04, 2005 at 11:54:12AM -0800, Brian T. Brunner wrote:
>
> My error: g77, g90, g95... the point being that if the new compiler
> is a true superset of the old (this is not true for gcc v3.4 which is not
> a true superset of gcc 2.97) then simple name links give everybody
> what they want and need.
>
gfortran does not implement all of the horrible hacks and
compiler flags found in g77, so a symlink of g77 pointing
at gfortran is inappropriate. That being said, I've found
very few Fortran 77 (with some extensions) packages that
gfortran can not compile.
--
Steve
next prev parent reply other threads:[~2005-11-04 20:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 19:54 Brian T. Brunner
2005-11-04 20:04 ` Steve Kargl [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-11-04 19:16 Nelson H. F. Beebe
2005-11-04 18:46 Brian T. Brunner
[not found] <436B7C69.C4A5DD32@nyu.edu>
[not found] ` <84fc9c000511040735h361e4430h32d43a82117c720@mail.gmail.com>
2005-11-04 16:00 ` Alex Tzanov
2005-11-04 16:04 ` Andrew Pinski
2005-11-04 16:10 ` Tobias.Schlueter
2005-11-04 16:10 ` Steve Kargl
2005-11-04 16:29 ` Richard E Maine
2005-11-04 16:30 ` Manfred Schwarb
2005-11-04 17:00 ` Steven Bosscher
2005-11-04 18:32 ` Jerry DeLisle
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=20051104200359.GB56800@troutmask.apl.washington.edu \
--to=sgk@troutmask.apl.washington.edu \
--cc=brian.t.brunner@gai-tronics.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-help@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).