[MacPorts] #65789: libgcc-devel @12-20220828_0+stdlib_flag build failure: use of undeclared identifier 'PTR'
MacPorts
noreply at macports.org
Mon Sep 26 08:29:15 UTC 2022
#65789: libgcc-devel @12-20220828_0+stdlib_flag build failure: use of undeclared
identifier 'PTR'
---------------------------+-----------------------
Reporter: physicsbeany | Owner: michaelld
Type: defect | Status: assigned
Priority: Normal | Milestone:
Component: ports | Version: 2.7.2
Resolution: | Keywords:
Port: libgcc-devel |
---------------------------+-----------------------
Comment (by cjones051073):
Replying to [comment:19 physicsbeany]:
> Replying to [comment:18 kencu]:
> > Two fast and effective solutions for you.
> >
> > 1. try {{{sudo port -v diagnose}}} and see what secrets it tells you.
There may be a quick fix in there.
> >
> > 2. start over. Sometimes it's just 1000x faster.
<https://guide.macports.org/chunked/installing.macports.uninstalling.html>
>
> Aha! I just tried suggestion number 1:
>
> {{{
> Error: currently installed version of Xcode, 14.0, is not supported by
MacPorts. For your currently installed system, only the following
versions of Xcode are supported: 13.4.1 13.4 13.3.1 13.3 13.2.1 13.2 13.1
> }}}
>
> ... but 2.7.2 is the most recent release of MacPorts, right? So does
this mean anything? Should I downgrade my XCode to 13.x? @cjones051073,
are you using XCode 14 too?
Yes I am. Ignore the above, it just means the supported list needs
updating.
Using archives is the default, so for you not to be must means you made
some change to your system that prevents it.
Did you edit /opt/local/etc/macports/macports.conf by chance ? Check what
is in there in relation to archives.
--
Ticket URL: <https://trac.macports.org/ticket/65789#comment:20>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list