public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Iain Sandoe <idsandoe@googlemail.com>
To: "C. David Whiteman" <davidwhiteman@mac.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: Compiler problem with gfortran
Date: Sun, 24 Apr 2022 20:20:58 +0100	[thread overview]
Message-ID: <F950C4A7-46F3-49A4-B9C9-7D3450AC8AAB@googlemail.com> (raw)
In-Reply-To: <D6936E54-88C0-4E7E-AA85-38A478BF77E9@mac.com>

Hello Dave,

> On 24 Apr 2022, at 20:10, C. David Whiteman <davidwhiteman@mac.com> wrote:
> 
> Thinking of trying another solution (screenshot follows)
> 
> <Screen Shot 2022-04-24 at 1.06.07 PM.png>
> 
> Does this seem to you like something worth trying??

Not something I am familiar with, and it seems highly unlikely that strange work-arounds would be needed if everything is properly installed.

The following occurs to me - on the basis that you have updated an existing Intel installation to an Arm64 / M1 one:

NOTE: the Arm64 (M1) installation of homebrew is in a different place from the Intel one.

(disclaimer; I’m not a homebrew dev) .. I would make sure that your PATH etc. are pointing to the Arm version (found in /opt/homebrew, I think) rather than the Intel install (which is usually in /usr/local) .. in case you copied across the Intel installation and/or configuration data.

I really would recommend raising a ticket with homebrew (if you are 100% sure that everything is installed as it should be) - since there is every reason to expect that a properly installed compiler will “just work" (there is no issue raised with me about this, from the homebrew folks).

thanks
Iain


      parent reply	other threads:[~2022-04-24 19:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-24 16:58 C. David Whiteman
2022-04-24 17:15 ` Jonathan Wakely
2022-04-24 17:19   ` Jonathan Wakely
     [not found]     ` <546813AC-1859-4DCC-A8CA-74F3CC0E4F83@mac.com>
2022-04-24 18:01       ` Jonathan Wakely
2022-04-24 18:32         ` Iain Sandoe
     [not found]           ` <EF85E3DB-4263-4266-9DCC-76E75ADF0C7B@mac.com>
     [not found]             ` <D6936E54-88C0-4E7E-AA85-38A478BF77E9@mac.com>
2022-04-24 19:20               ` Iain Sandoe [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=F950C4A7-46F3-49A4-B9C9-7D3450AC8AAB@googlemail.com \
    --to=idsandoe@googlemail.com \
    --cc=davidwhiteman@mac.com \
    --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).