public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alex Tzanov <alex.tzanov@nyu.edu>
To: fortran@gcc.gnu.org, gcc-help@gcc.gnu.org
Subject: Re: F77 code under gcc
Date: Fri, 04 Nov 2005 16:00:00 -0000	[thread overview]
Message-ID: <436B84F9.5F386051@nyu.edu> (raw)
In-Reply-To: <84fc9c000511040735h361e4430h32d43a82117c720@mail.gmail.com>

Dear Sir


I am redirected my question to you following the advise by gcc developer.

From your site:

http://gcc.gnu.org/gcc-4.0/changes.html#4.0.2

Fortran

    * A new Fortran front end has replaced the aging GNU Fortran 77 front end. The new front
end supports Fortran 90 and Fortran 95. It may not yet be as stable as the old Fortran front
end.

So shall I understand no support for F77 at all? Or there are options for F77 dialect?
Novell site claims support for F77, but seems to me that is not true.


Richard Guenther wrote:

> On 11/4/05, Alex Tzanov <alex.tzanov@nyu.edu> wrote:
> > Dear developers,
> >
> >
> > I have recently upgraded my PC to Suse Linux 10 (from 9.3). The
> > distribution
> > comes with gcc 4.0.2. The problem that arrised after the upgrade is that
> > I
> > cannot compile f77 codes anymore. More precisely when I try to compile a
> >
> > Fortran file (*.f) I am getting the error:
> >
> > "gcc: installation problem, cannot exec 'f951': No such file or
> > directory
>
> First of all, you should report installation problems of vendor packages
> to the vendor, i.e. SUSE or NOVELL in this case.  Second, this list
> is for development _of_ gcc, not with, for such kind of questions please
> refer to gcc-help@gcc.gnu.org.
>
> You are probably missing an installed rpm, like gcc-fortran or whatever
> it is called.
>
> Thanks,
> Richard.
>
> >
> >
> > This is rather confusing since Novell claims that the provided rpm
> >
> > has been created with support of F77. Assuming the problem could come from
> >
> > formated input I tried
> >
> > -ffree-form
> >
> > -x f77
> >
> > but nothing works. Do you have any clue about that? How I can compile F77 code or should I
> >
> > downgrade to gcc 2.95 or 3.0.x?
> >
> > Thank you
> >
> > Alexander
> >
> > --
> > Alexander Tzanov
> > Scientific Computing and Visualization
> > New York University, WWH
> > 251 Mercer Street
> > phone: 212 998 3159
> > fax:   212 995 4120
> > e-mail: alex.tzanov@nyu.edu
> >
> >
> >
> >

--
Alexander Tzanov
Scientific Computing and Visualization
New York University, WWH
251 Mercer Street
phone: 212 998 3159
fax:   212 995 4120
e-mail: alex.tzanov@nyu.edu



       reply	other threads:[~2005-11-04 16:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <436B7C69.C4A5DD32@nyu.edu>
     [not found] ` <84fc9c000511040735h361e4430h32d43a82117c720@mail.gmail.com>
2005-11-04 16:00   ` Alex Tzanov [this message]
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
2005-11-04 18:46 Brian T. Brunner
2005-11-04 19:16 Nelson H. F. Beebe
2005-11-04 19:54 Brian T. Brunner
2005-11-04 20:04 ` Steve Kargl

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=436B84F9.5F386051@nyu.edu \
    --to=alex.tzanov@nyu.edu \
    --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).