public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Iain Sandoe <idsandoe@googlemail.com>
To: -xlan- <ahsan.ahmed3246@gmail.com>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: Failure During Building
Date: Sat, 18 Feb 2023 23:49:23 +0000	[thread overview]
Message-ID: <4E479E20-5C2D-4CCA-8446-1D1FD6BAB8E5@googlemail.com> (raw)
In-Reply-To: <CAOZ-8gVxoxPBO4FmAKDmHvw1M70r7QQpV_vqkOonnF1BWf6UKw@mail.gmail.com>

Hi

> On 18 Feb 2023, at 20:28, -xlan- <ahsan.ahmed3246@gmail.com> wrote:
> 
> I tried compiling version 12.2.0 and it attempts to access system headers at /usr/include, but on mac the system headers are stored at 
> /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/include.

For supported x86_64 GCC versions (at present 12 and trunk) on macOS12.

It is usually easiest to install the Xcode Command Line Tools - the SDK path is then /Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk

then add the following to your configure line:

—with-sysroot=/Library/Developer/CommandLineTools/SDKs/MacOSX12.sdk

If you want to use the set in Xcode then add the following to your configure line:

—with-sysroot=`xcrun --show-sdk-path`

I prefer/recommend the first option.
HTH,
Iain



  reply	other threads:[~2023-02-18 23:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17 15:17 -xlan-
2023-02-17 15:37 ` Jonathan Wakely
2023-02-17 16:03   ` Iain Sandoe
2023-02-18 20:28     ` -xlan-
2023-02-18 23:49       ` Iain Sandoe [this message]
2023-02-19 16:27         ` -xlan-
2023-02-19 16:48           ` Iain Sandoe
2023-02-19 16:56             ` -xlan-

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=4E479E20-5C2D-4CCA-8446-1D1FD6BAB8E5@googlemail.com \
    --to=idsandoe@googlemail.com \
    --cc=ahsan.ahmed3246@gmail.com \
    --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).