From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Chris Johns <chris@contemporary.net.au>
Cc: GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: Building gcc-12 on MacOS Ventura (aarch64)
Date: Fri, 24 Mar 2023 23:07:50 +0000 [thread overview]
Message-ID: <CAH6eHdTQJ=ugFmNk+y_DGbPbigjC6yO40Bz=8GJP0ax4ifrVaA@mail.gmail.com> (raw)
In-Reply-To: <CAH6eHdRUK=vz4zOmuNfq1VdfchQSWEuaZbUDicPVixv9iMWcMw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 964 bytes --]
On Fri, 24 Mar 2023, 23:07 Jonathan Wakely, <jwakely.gcc@gmail.com> wrote:
>
>
> On Fri, 24 Mar 2023, 23:03 Chris Johns, <chris@contemporary.net.au> wrote:
>
>> Hi,
>>
>> I am sorting out some issues building RTEMS on MacOS including the M
>> processors.
>> The building gcc-12.2.1 for the few architectures I tested fail with sig
>> faults
>> in xgcc when building the runtime. I tried arm, aarch64 and sparc. As a
>> result I
>> wondered about bootstrapping gcc and using that to build the tools rather
>> than
>> clang from Xcode.
>>
>> Is aarch64-apple-darwin supported?
>
>
>
> No. Iain Sandoe has some personal branches with changes to support it, but
> the changes are not in the official gcc repo yet. If you search the
> gcc-help@gcc.gnu.org list you'll find links to his code. I think Homebrew
> is his patches too.
>
*uses his patches too.
>
> I am seeing:
>>
>> *** Configuration aarch64-apple-darwin22.3.0 not supported
>>
>> Thanks
>> Chris
>>
>
next prev parent reply other threads:[~2023-03-24 23:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 23:02 Chris Johns
2023-03-24 23:07 ` Jonathan Wakely
2023-03-24 23:07 ` Jonathan Wakely [this message]
2023-03-24 23:51 ` Chris Johns
2023-03-25 0:08 ` Stuff Received
2023-03-26 1:05 ` Chris Johns
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='CAH6eHdTQJ=ugFmNk+y_DGbPbigjC6yO40Bz=8GJP0ax4ifrVaA@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=chris@contemporary.net.au \
--cc=gcc@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).