Re: what's with the C++ extension?

> On 18 Sep 2022, at 11:58 pm, Chris Jones wrote: > >  > > >>> On 18 Sep 2022, at 1:29 pm, René J.V. Bertin wrote: >>> >> Hi, >> >> Building C++ code that does >> >> #include >> >> I get either a file-not-found error or a bunch of errors that the functions >> are 10.15+ only. What's

Re: what's with the C++ extension?

> On 18 Sep 2022, at 1:29 pm, René J.V. Bertin wrote: > > Hi, > > Building C++ code that does > > #include > > I get either a file-not-found error or a bunch of errors that the functions > are 10.15+ only. What's with that? Seems pretty clear to me… > If the implementation is provided

Re: what's with the C++ extension?

On Sunday September 18 2022 14:29:07 René J.V. Bertin wrote: >On more recent systems that have a stock libc++ one can install `port:libcxx` >with the binaries under $prefix . I have been doing that for years so all >MacPorts executables use it, and that has never caused any ABI issues with

Re: Disabled key in launchd plists

On Sunday September 18 2022 00:55:59 Ryan Schmidt wrote: >I don't think I have anything further I want to add to this conversation. I've >explained to the best of my knowledge how launchd/launchctl work and what >MacPorts does with its launchd support and why. I'm sure you can perform any

what's with the C++ extension?

Hi, Building C++ code that does #include I get either a file-not-found error or a bunch of errors that the functions are 10.15+ only. What's with that? If the implementation is provided by libc++, isn't this something that could be patched? Shouldn't require any external dependencies on