public inbox for fortran@gcc.gnu.org
 help / color / mirror / Atom feed
From: Iain Sandoe <iain@sandoe.co.uk>
To: Leigh House <hagar@newmexico.com>
Cc: GCC Fortran <fortran@gcc.gnu.org>
Subject: Re: What .dylib files does gfortran v 11.2.0 need on a Mac?
Date: Sat, 22 Jul 2023 20:14:09 +0100	[thread overview]
Message-ID: <040FC6F8-CA4D-4ECB-B712-E51238F794EC@sandoe.co.uk> (raw)
In-Reply-To: <D86384C6-EA0E-4B5A-A99F-9BE81F1BE84D@newmexico.com>

Hi Leigh,

> On 22 Jul 2023, at 20:05, Leigh House <hagar@newmexico.com> wrote:
> 

> Thanks for your fast reply!
> 
> My Mac is an intel iMac from 2019. 

That should be fine with “upstream” sources, should you decide to build from source (but that should not be necessary, there are several places providing gfortran for mac).

> I didn’t keep detailed notes about where I got the compiler package, though I’ve often gone to hpc.sourceforge.net in the past, under “Computation Tools”. I suspect that is where I got my current compiler from. 
> 
> And I didn’t keep notes about which .dylib file I had to find and copy into /usr/local/lib, though from a colleague’s experience it may have been libgfortran.5.dylib.

I checked the version(s) for which the initialization bug is fixed:

GCC-10.4
GCC-11.3 <<- so you are almost certainly seeing it with 11.2.
GCC-12.1
GCC-13.1
(and current development ’trunk’).

This was a very unusual case - we try to be backward compatible as much as possible, but the change was out of our hands.

So, I’d recommend that you see if your “usual source” has an update - or, alternately, go to one of the ‘OSS distributions’ like Homebrew.

HTH,
Iain


  reply	other threads:[~2023-07-22 19:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-22 18:20 Leigh House
2023-07-22 18:49 ` Iain Sandoe
2023-07-22 19:05   ` Leigh House
2023-07-22 19:14     ` Iain Sandoe [this message]
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=040FC6F8-CA4D-4ECB-B712-E51238F794EC@sandoe.co.uk \
    --to=iain@sandoe.co.uk \
    --cc=fortran@gcc.gnu.org \
    --cc=hagar@newmexico.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).