From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: -xlan- <ahsan.ahmed3246@gmail.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Failure During Building
Date: Fri, 17 Feb 2023 15:37:42 +0000 [thread overview]
Message-ID: <CAH6eHdT4fthJ0201B0n0eOHbFamN3=9WR0jVAE7pC=1rX9cHCw@mail.gmail.com> (raw)
In-Reply-To: <CAOZ-8gW2k_r2zBz04u1_EHGnY_dp0O8iivdWyj9eVJFF9o0Ruw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]
On Fri, 17 Feb 2023, 15:17 -xlan- via Gcc, <gcc@gcc.gnu.org> wrote:
> I was building gcc version 4.9.1
Why?
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.
/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/include/c++/v1/__config:858:15:
> note: expanded from macro '_VSTD'
> #define _VSTD std::_LIBCPP_ABI_NAMESPACE
> ^
> ../../gcc-4.9.1/gcc/system.h:685:13: note: 'fancy_abort' declared here
> extern void fancy_abort (const char *, int, const char *)
> ATTRIBUTE_NORETURN;
> ^
> 1 error generated.
> make[1]: *** [c/c-objc-common.o] Error 1
> make: *** [all-gcc] Error 2
>
> Mac OS: Monterey 12.6.4
>
next prev parent reply other threads:[~2023-02-17 15:37 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 [this message]
2023-02-17 16:03 ` Iain Sandoe
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='CAH6eHdT4fthJ0201B0n0eOHbFamN3=9WR0jVAE7pC=1rX9cHCw@mail.gmail.com' \
--to=jwakely.gcc@gmail.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).