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
> 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
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
>
>
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
>
FYI clang-8.0, new default on 10.6.8, is very strict
appears will have to add to blacklist on many ports
or otherwise surgerize code/standard setting — eventually will have to happen
but all at once is daunting
downgrading default compiler on 10.6.8 to clang-5.0 gets the rev-upgrade done
once
Hi,
I already mentioned this in the past, but I would like to repeat.
When someone opens our homepage and wants to download MacPorts using
Safari on, say, 10.6, the download link from GitHub doesn't work, and
it's not trivial for users to find out the alternative link
