From: Andrew Pinski <pinskia@gmail.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: "Lingadahally,
Vishakha (2023)" <Vishakha.Lingadahally.2023@live.rhul.ac.uk>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: Re: gfortran: error: unrecognized argument in option '-mcmodel=medium'
Date: Wed, 27 Sep 2023 00:25:32 -0700 [thread overview]
Message-ID: <CA+=Sn1kK7aLnf2V5Zrzgo5y3E8HaKe6cfgx3bQuTAALQWMW_HA@mail.gmail.com> (raw)
In-Reply-To: <CAFiYyc3auu56pG7ktZQK4_zhQVG2zwNtrq66c0ocwUYvoLZyDw@mail.gmail.com>
On Tue, Sep 26, 2023 at 11:39 PM Richard Biener via Fortran
<fortran@gcc.gnu.org> wrote:
>
> On Tue, Sep 26, 2023 at 4:44 PM Lingadahally, Vishakha (2023)
> <Vishakha.Lingadahally.2023@live.rhul.ac.uk> wrote:
> >
> > Dear GCC Team,
> >
> > I'm running Ubuntu 22 on my Mac virtually and my gfortran version is 11.4.0. When I try to install a certain software package, I encounter the following error:
> >
> > gfortran: error: unrecognized argument in option '-mcmodel=medium'
> > gfortran: note: valid arguments to '-mcmodel=' are: large small tiny
> >
> > Is this due to attempting to run gfortran on arm64 architecture? Could you please let me know how I could resolve the issue?
>
> You have to turn to Ubuntu here, -mcmodel=medium is certainly
> supported in GCC 11, maybe Ubuntu patches out
> the support?
Well -mcmodel=medium is the x86_64 specific option while they are
trying to run on aarch64 which has a different set options.
>
> >
> > Thank you
> >
> > Warm regards,
> > Vishakha
> >
> > This email, its contents and any attachments are intended solely for the addressee and may contain confidential information. In certain circumstances, it may also be subject to legal privilege. Any unauthorised use, disclosure, or copying is not permitted. If you have received this email in error, please notify us and immediately and permanently delete it. Any views or opinions expressed in personal emails are solely those of the author and do not necessarily represent those of Royal Holloway, University of London. It is your responsibility to ensure that this email and any attachments are virus free.
next prev parent reply other threads:[~2023-09-27 7:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 14:44 Lingadahally, Vishakha (2023)
2023-09-27 6:37 ` Richard Biener
2023-09-27 7:25 ` Andrew Pinski [this message]
2023-09-27 7:33 ` Iain Sandoe
2023-09-27 7:35 ` Iain Sandoe
2023-09-28 13:56 ` [EXT] " Lingadahally, Vishakha (2023)
2023-09-28 16:00 ` [EXT] " Iain Sandoe
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='CA+=Sn1kK7aLnf2V5Zrzgo5y3E8HaKe6cfgx3bQuTAALQWMW_HA@mail.gmail.com' \
--to=pinskia@gmail.com \
--cc=Vishakha.Lingadahally.2023@live.rhul.ac.uk \
--cc=fortran@gcc.gnu.org \
--cc=richard.guenther@gmail.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).