One of those posts mentioned downgrading the XCode command line tools and
that having
resolved the issue, implying a bug on Apple's side introducing a breaking
change.
What remains to be resolved is whether Apple or GCC will change in response.
On Fri, Sep 22, 2023 at 9:20 AM Christopher Jones
>
> Workaround, for now, is to not use gcc to build C++ sources. Clang is anyway
> the default compiler on Mac’s, and is what MacPorts uses for the vast
> majority of ports, so if you can use clang++ (either Xcode or MacPorts own
> builds). Both these are still fine.
Or, of course,
> On 22 Sep 2023, at 1:27 pm, Christopher Jones
> wrote:
>
>
>
>> On 22 Sep 2023, at 1:09 pm, Carlo Tambuatco wrote:
>>
>> macOS 13.5.2
>> package-id: com.apple.pkg.CLTools_Executables
>> version: 15.0.0.0.1.1694021235
>>
>> My g++-mp-12 (from gcc version 12) install on macports started
> On 22 Sep 2023, at 1:09 pm, Carlo Tambuatco wrote:
>
> macOS 13.5.2
> package-id: com.apple.pkg.CLTools_Executables
> version: 15.0.0.0.1.1694021235
>
> My g++-mp-12 (from gcc version 12) install on macports started giving me
> these errors compiling
> C++ programs after upgrading my
macOS 13.5.2
package-id: com.apple.pkg.CLTools_Executables
version: 15.0.0.0.1.1694021235
My g++-mp-12 (from gcc version 12) install on macports started giving me these
errors compiling
C++ programs after upgrading my XCode command line tools a few days ago.
Is this something macports will
macOS 13.5.2
package-id: com.apple.pkg.CLTools_Executables
version: 15.0.0.0.1.1694021235
My g++-mp-12 (from gcc version 12) install on macports started giving me
these errors compiling
C++ programs after upgrading my XCode command line tools a few days ago.
Is this something macports will
