Re: stdlib.h compilation error for macports gcc9.

On Feb 8, 2021, at 12:34, Ken Cunningham wrote: > On 2021-02-08, at 10:02 AM, Ryan Schmidt wrote: > >> On Feb 7, 2021, at 17:57, Ken Cunningham wrote: >> >>> Perhaps we should find a way to broaden that down to including MacOSX10.15+ >>> as well, if Catalina is going to be using the MacOSX11.x

Re: stdlib.h compilation error for macports gcc9.

On Feb 7, 2021, at 17:57, Ken Cunningham wrote: > Perhaps we should find a way to broaden that down to including MacOSX10.15+ > as well, if Catalina is going to be using the MacOSX11.x SDK. Why stop at 10.15? For several macOS versions before that, the last compatible Xcode version might

Re: stdlib.h compilation error for macports gcc9.

Our fix changed the baked-in gcc SDK reference from using the MacOSX11.x  and above  to MacOSX.sdk. that fixes a number of broken systems, but not all it appears. Perhaps we should find a way to broaden that down to including MacOSX10.15+ as well, if Catalina is going to be using the

Re: stdlib.h compilation error for macports gcc9.

> On 7 Feb 2021, at 11:25 pm, Carlo Tambuatco wrote: > >  > > >> On Feb 7, 2021, at 6:18 PM, Christopher Jones >> wrote: >> >> >> what happens if you set SDKROOT and then try again >> >> export SDKROOT=`xcrun --show-sdk-path` >> >> ? >> > > > Hm… that seems to have done the trick.

Re: stdlib.h compilation error for macports gcc9.

> On Feb 7, 2021, at 6:18 PM, Christopher Jones > wrote: > > > what happens if you set SDKROOT and then try again > > export SDKROOT=`xcrun --show-sdk-path` > > ? > Hm… that seems to have done the trick. So, what changed between upgrades to gcc9…? It worked fine before. >> On 7

Re: stdlib.h compilation error for macports gcc9.

what happens if you set SDKROOT and then try again export SDKROOT=`xcrun --show-sdk-path` ? > On 7 Feb 2021, at 11:12 pm, Carlo Tambuatco wrote: > > > >> On Feb 7, 2021, at 5:39 PM, Christopher Jones > > wrote: >> >> macOS 11 brought big changes to how

Re: stdlib.h compilation error for macports gcc9.

> On Feb 7, 2021, at 5:39 PM, Christopher Jones > wrote: > > macOS 11 brought big changes to how Apple versions its SDKs. They now > potentially change each minor update, and as such we had to figure out how to > deal with this. > > gcc is built against a specific SDK, and to handle this

Re: stdlib.h compilation error for macports gcc9.

macOS 11 brought big changes to how Apple versions its SDKs. They now potentially change each minor update, and as such we had to figure out how to deal with this. gcc is built against a specific SDK, and to handle this unpredictably it was recently changed to use the unversioned SDK, instead

Re: stdlib.h compilation error for macports gcc9.

Well what's odd is I'm only getting this error after upgrading to the latest macports gcc9. Indeed when I use the XCode provided clang version of gcc, it finds all the required libraries. My CPATH environment variable was sufficient to specify the locations of the libraries before the upgrade, so

Re: stdlib.h compilation error for macports gcc9.

It sounds like your builds are not correctly specifying the SDK gcc is to use. There are a number of ways you can do this, either by pass it via a compiler flag, by running the complication through xcrun, or by setting the SDKROOT variables to the required path. Cheers Chris > On 7 Feb

stdlib.h compilation error for macports gcc9.

I don’t know if this is a result of updating to the latest macports gcc9, or the update of XCode, but all of a sudden when I try to build my C++ program which includes I get this strange chain reaction of errors. In file included from /opt/local/include/gcc9/c++/ext/string_conversions.h:41,