public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: ALAN P VONDEROHE <vonderoh@engr.wisc.edu>
To: "jwakely.gcc@gmail.com" <jwakely.gcc@gmail.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: RE: problem with opening files
Date: Mon, 6 Apr 2020 14:17:25 +0000	[thread overview]
Message-ID: <BN8PR06MB616280257FEEA60AD9D78A6E9DC20@BN8PR06MB6162.namprd06.prod.outlook.com> (raw)
In-Reply-To: <CAH6eHdSCvsfsCHx_5vWXL6GiOPmdx83RjBUpor_YJWji+14-gg@mail.gmail.com>

Thanks for the quick reply.

I mean executable (.exe) FORTRAN programs that were compiled a few months ago and have worked perfectly until three days ago, no longer work. They cannot open files. 

In addition, new programs, that I compile and link today into executables, do not work. They cannot open files.

I use GCC version 5.2.0 to compile and link. I have been using it since September, 2019 and have never changed versions.

Alan Vonderohe

-----Original Message-----
From: jwakely.gcc@gmail.com <jwakely.gcc@gmail.com> 
Sent: Sunday, April 5, 2020 3:53 PM
To: ALAN P VONDEROHE <vonderoh@engr.wisc.edu>
Cc: gcc-help@gcc.gnu.org
Subject: Re: problem with opening files

On Sun, 5 Apr 2020 at 20:15, ALAN P VONDEROHE via Gcc-help <gcc-help@gcc.gnu.org> wrote:
>
> Hello,
>
> All of a sudden, none of my FORTRAN programs can open files. Programs that opened files last week, cannot open them now. Any suggestions?

I suggest reading http://www.catb.org/esr/faqs/smart-questions.html
and I suggest you provide MUCH more information. Nobody can usefully answer this.

Do you mean your code no longer works when it is recompiled? Or binaries that were already compiled just stopped working? Or something else?

Are you even using GCC to compile your code? Which version? Did you change the version in the last week?

      reply	other threads:[~2020-04-06 14:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-05 18:58 ALAN P VONDEROHE
2020-04-05 20:53 ` Jonathan Wakely
2020-04-06 14:17   ` ALAN P VONDEROHE [this message]

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=BN8PR06MB616280257FEEA60AD9D78A6E9DC20@BN8PR06MB6162.namprd06.prod.outlook.com \
    --to=vonderoh@engr.wisc.edu \
    --cc=gcc-help@gcc.gnu.org \
    --cc=jwakely.gcc@gmail.com \
    /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).