public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "matthew.thompson at nasa dot gov" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/90330] gcc 9.1.0 fails to install on macOS 10.14.4
Date: Thu, 25 Mar 2021 14:00:30 +0000	[thread overview]
Message-ID: <bug-90330-4-BM2veLd9cB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-90330-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90330

--- Comment #34 from Matt Thompson <matthew.thompson at nasa dot gov> ---
Iain,

Apologies. I forgot about this. Seeing as I'm now using GNU 10.2.0 on my
Macbook...I guess it's working.

I currently do:

../gcc-10.2.0/configure --prefix=$HOME/installed/Core/gcc-gfortran/10.2.0
--enable-languages=c,c++,fortran
--with-sysroot=/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk |& tee
configure.log

when I configure it which is much as you suggested.

My guess is I worked with my admins nuking and restoring XCode until we got it
right (or something, government laptops are fun, no sudo, lots of
restrictions...).

Thanks for your help, and I can't wait for 10.3 or 11.0 or whatever is next! N

Note: I'm still on an Intel Mac, so I won't need to bother "Iain Sandoe, master
of M1 GNU" about that for a while. :D

  parent reply	other threads:[~2021-03-25 14:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-90330-4@http.gcc.gnu.org/bugzilla/>
2021-03-24 20:06 ` iains at gcc dot gnu.org
2021-03-25 14:00 ` matthew.thompson at nasa dot gov [this message]
2021-03-26 13:31 ` iains at gcc dot gnu.org

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=bug-90330-4-BM2veLd9cB@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).