public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Leigh House <hagar@newmexico.com>
To: fortran@gcc.gnu.org
Subject: What .dylib files does gfortran v 11.2.0 need on a Mac?
Date: Sat, 22 Jul 2023 12:20:22 -0600	[thread overview]
Message-ID: <DE8404F9-6E96-4980-A491-27F27CC20F14@newmexico.com> (raw)

I’ve not been able to get any output written to a file by a program I compiled with gfortran v11.2.0 on my Mac. The Mac has MacOS Monterey (v12.6.7). This seems like a simple problem, yet I’ve not been able to find a solution. And it is an increasing obstacle for me. The problem includes fortran programs that were compiled years ago. Suddenly, they can no longer write output to a file. For example, writing to standard out (lun 6) works fine to the screen, but when redirected to a file, that file is empty.

A colleague got a clue that the problem may be in an out-of-date, faulty or corrupted .dylib file. Perhaps /usr/local/lib/libgfortran.5.dylib? The file /usr/local/lib/libgfortran.dylib is a symbolic link to /usr/local/lib/libgfortran.5.dylib. That file has a date of Nov 9, 2021 on my Mac. Should I have a newer file? If so, how do I get it? I would have thought it would be included in the gfortran install, but maybe not?

More generally, can I get a list of the .dylib files that gfortran (11.2.0) and gcc (also 11.2.0) need for programs they compile to function properly? And the dates for them? Do these files need to be owned by user “root” or have other special permissions (on my Mac, I own them as a regular user).

This seems like a very obscure, yet debilitating problem that I have encountered. If I cannot write or modify my fortran codes and have them work properly, I am SOL. 

Thanks very much for your help,

Leigh House, Los Alamos, NM



             reply	other threads:[~2023-07-22 18:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-22 18:20 Leigh House [this message]
2023-07-22 18:49 ` Iain Sandoe
2023-07-22 19:05   ` Leigh House
2023-07-22 19:14     ` Iain Sandoe
2023-07-22 22:25       ` Leigh House

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=DE8404F9-6E96-4980-A491-27F27CC20F14@newmexico.com \
    --to=hagar@newmexico.com \
    --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).