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>,
	Jonathan Wakely <jwakely.gcc@gmail.com>
Subject: Re: Failure During Building
Date: Fri, 17 Feb 2023 16:03:59 +0000	[thread overview]
Message-ID: <3FB34CBA-3065-4596-994D-D666BFA7B632@googlemail.com> (raw)
In-Reply-To: <CAH6eHdT4fthJ0201B0n0eOHbFamN3=9WR0jVAE7pC=1rX9cHCw@mail.gmail.com>



> On 17 Feb 2023, at 15:37, Jonathan Wakely via Gcc <gcc@gcc.gnu.org> wrote:
> 
> On Fri, 17 Feb 2023, 15:17 -xlan- via Gcc, <gcc@gcc.gnu.org> wrote:
> 
>> I was building gcc version 4.9.1
> 
> 
> Why?

Indeed, what is the use-case?
trying to build such an old GCC version on modern macOS could be problematic.

> on Mac OS version when I got this error:
>> 
>> In file included from ../../gcc-4.9.1/gcc/c/c-objc-common.c:33:
>> In file included from
>> 
>> /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/v1/new:93:
>> 
>> /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/v1/exception:184:5:
>> error: no member named 'fancy_abort' in namespace 'std::__1'; did you mean
>> simply 'fancy_abort'?
>>    _VSTD::abort();
>>    ^~~~~~~
>> 
> 
> 
> The GCC sources define 'abort' as a macro, which appears to be incompatible
> with LLVM's libc++.
> 
> You might be able to compile using -stdlib=libstdc++ instead.

There are no headers for libstdc++ in SDKs for OSX 10.13 + (so you would need also to find an
older SDK and then build with an OSX target of say 10.12).

What you are trying to do is going to required quite advanced techniques to deal with the difference in the OS, compiler and bootstrap tools.  I have not attempted anything < GCC-5 on newer machines.

Iain




  reply	other threads:[~2023-02-17 16:04 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 [this message]
2023-02-18 20:28     ` -xlan-
2023-02-18 23:49       ` Iain Sandoe
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=3FB34CBA-3065-4596-994D-D666BFA7B632@googlemail.com \
    --to=idsandoe@googlemail.com \
    --cc=ahsan.ahmed3246@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jwakely.gcc@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).