public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Stuff Received <stuff@riddermarkfarm.ca>
To: gcc@gcc.gnu.org
Subject: Re: [GSoC] Help needed for building on aarch64-apple-darwin22.1.0
Date: Tue, 21 Feb 2023 12:13:02 -0500	[thread overview]
Message-ID: <012c54ce-9654-f0a7-e559-1d373e83d703@riddermarkfarm.ca> (raw)
In-Reply-To: <AC27F203-CF8A-4C25-8AF4-A5D94520AAFB@googlemail.com>

Greetings, Iaian.

On 2023-02-20 12:42, Iain Sandoe wrote:
> Hi Shengyu,
> 
>> On 20 Feb 2023, at 17:31, Shengyu Huang via Gcc <gcc@gcc.gnu.org> wrote:
>>
> 
>> After following the instructions here (https://gcc.gnu.org/wiki/InstallingGCC) and here (https://gcc.gnu.org/install/index.html), the `make` step simply fails with “*** Configuration aarch64-apple-darwin22.1.0 not supported”. I found this issue on Bugzilla (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96168), but the status says it’s suspended. Does it mean there is no way I can build from source on my new laptop? My old MBP was unfortunately broken two months ago, so the new laptop with Apple M2 is the only device I have at the moment.
> 
> I have a development branch for trunk here :
>    https://github.com/iains/gcc-darwin-arm64

This is wonderful -- thank you for doing this!

I am not interested in gfortran but rather gm2 and your branch for the 
trunk works quite well.

Sincerely,
john


> and for GCC-12 here:
>   https://github.com/iains/gcc-12-branch
> 
> until I have some time to upstream the work (which could not be before GCC-14, I think) you can use these.
> 
> HTH,
> Iain
> 


      reply	other threads:[~2023-02-21 17:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20 17:31 Shengyu Huang
2023-02-20 17:42 ` Iain Sandoe
2023-02-21 17:13   ` Stuff Received [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=012c54ce-9654-f0a7-e559-1d373e83d703@riddermarkfarm.ca \
    --to=stuff@riddermarkfarm.ca \
    --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).