public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Brian T. Brunner" <brian.t.brunner@gai-tronics.com>
To: <fortran@gcc.gnu.org>, <gcc-help@gcc.gnu.org>
Subject: Re: F77 code under gcc
Date: Fri, 04 Nov 2005 19:54:00 -0000	[thread overview]
Message-ID: <s36b4bf1.052@CRPSPKWANW02-IA.hubbell.com> (raw)


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.

Brian Brunner
brian.t.brunner@gai-tronics.com
(610)796-5838

>>> "Nelson H. F. Beebe" <beebe@math.utah.edu> 11/04/05 02:16PM >>>
Brian T. Brunner <brian.t.brunner@gai-tronics.com> writes on 
Fri, 04 Nov 2005 10:45:51 -0800:

>> I would recommend to the package-wrapper folks to put a sym link
>> named f77 alongside f90 & f95 & gfortran.

Please do NOT do that.  The gcc family runs on many different
operating systems where there are already vendor-provided compilers
named f77, f90, and f95.  Historically, the GNU compilers have had
names like gcc, g++, g77, gpc, gnat, gfortran, ..., avoiding name
collisions with compiler products from other suppliers.  It is
generally only in the GNU/Linux and BSD worlds that the GNU compilers
have also been installed in /usr/bin under the names cc and f77.

Let's keep distinctive names for the GNU compilers.

-------------------------------------------------------------------------------
- Nelson H. F. Beebe                    Tel: +1 801 581 5254                  -
- University of Utah                    FAX: +1 801 581 4148                  -
- Department of Mathematics, 110 LCB    Internet e-mail: beebe@math.utah.edu  -
- 155 S 1400 E RM 233                       beebe@acm.org  beebe@computer.org -
- Salt Lake City, UT 84112-0090, USA    URL: http://www.math.utah.edu/~beebe  -
-------------------------------------------------------------------------------

*******************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept
for the presence of computer viruses.

www.hubbell.com - Hubbell Incorporated

             reply	other threads:[~2005-11-04 19:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-04 19:54 Brian T. Brunner [this message]
2005-11-04 20:04 ` Steve Kargl
  -- 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     ` Steve Kargl
2005-11-04 16:10     ` Tobias.Schlueter
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=s36b4bf1.052@CRPSPKWANW02-IA.hubbell.com \
    --to=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).