Beyond the /usr/include issue, Xcode 11 should be problematic when its
bundled 10.15 SDK is used under either Mojave or Catalina due to the
enforced use of the availability attribute in the headers.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90835
On Wed, Sep 25, 2019 at 5:46 AM Chris Jones
(*) The package to add back /usr/include currently does not exist in
10.15 beta, so unless it reappears come final release this is going to
be more of a problem there….
This package is not going to be coming back:
Saagar Jha
> On Sep 24, 2019, at 01:56, Christopher Jones wrote:
>
> Hi,
>
> Note the error is not specific to gcc. Macports clang has the same problem.
>
> > clang++-mp-8.0 -O3 ./main.cpp
> In file included from ./main.cpp:1:
> In file included from
>
> The issue is both macports clang and gcc rely (by default) on /usr/include
> being present, and this is no longer present by default with Xcode 11
Not exactly. The full logic was outlined by Jeremy here:
https://trac.macports.org/ticket/57612#comment:18
Hi,
Note the error is not specific to gcc. Macports clang has the same problem.
> clang++-mp-8.0 -O3 ./main.cpp
In file included from ./main.cpp:1:
In file included from
/opt/local/libexec/llvm-8.0/bin/../include/c++/v1/iostream:38:
In file included from
On 2019-9-24 15:31 , Mihir Luthra wrote:
> Hi,
>
> After the xcode update, there have been many question on stackoverflow
> regarding gcc and g++ linking fails. Any ideas on what can be done?
>
> https://stackoverflow.com/questions/58072318/cannot-link-any-c-program-with-gcc-on-mac-mojave
>
>
Hi,
After the xcode update, there have been many question on stackoverflow
regarding gcc and g++ linking fails. Any ideas on what can be done?
https://stackoverflow.com/questions/58072318/cannot-link-any-c-program-with-gcc-on-mac-mojave
