From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Marina Marjanovic <marina.marjanovic.1@ulaval.ca>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: MacBook Pro M1
Date: Thu, 13 Jan 2022 08:18:41 +0000 [thread overview]
Message-ID: <CAH6eHdS92=fL3xTazGucVDawkmogPZHsfGp0SKWfRL2OvBOWmQ@mail.gmail.com> (raw)
In-Reply-To: <YT1PR01MB4009E8E05B51C2E900615FDEF4539@YT1PR01MB4009.CANPRD01.PROD.OUTLOOK.COM>
On Thu, 13 Jan 2022, 01:55 Marina Marjanovic via Gcc-help, <
gcc-help@gcc.gnu.org> wrote:
> Hi,
>
> My name is Marina Marjanovic and I am currently working on my master
> degree and I need gcc7 to make it work with MESH(
> https://wiki.usask.ca/pages/viewpage.action?pageId=1935648493 ). But I
> had a MacBook air 2015 and everything was working fine, so I got a new
> MacBook pro M1 and nothing is working anymore.
>
> I have some issues with gcc on a new MacBook Pro, ship M1 pro. I need
> gcc7, but I have an error message saying : gcc@7: The x86_64 architecture
> is required for this software.
>
> And the new version of gcc11, is not working with MESH….
> I am wondering what can I do to make it work? Can you help me?
>
GCC 7 is no longer supported or maintained, so it's not going to get
updated to work on the new Apple M1 systems. GCC 10 is the oldest release
series that will work on M1 right now.
You should try to reach out to the MESH folks for a solution (it might be
that it would run under Rosetta 2 - so that intel install can be made on
the M1) - of course that’s not going to be the best performance. Or maybe
they can fix it to make it work with a recent GCC.
prev parent reply other threads:[~2022-01-13 8:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 1:53 Marina Marjanovic
2022-01-13 8:18 ` Jonathan Wakely [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='CAH6eHdS92=fL3xTazGucVDawkmogPZHsfGp0SKWfRL2OvBOWmQ@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=marina.marjanovic.1@ulaval.ca \
/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).