[MacPorts] #65789: libgcc-devel @12-20220828_0+stdlib_flag build failure: use of undeclared identifier 'PTR'
MacPorts
noreply at macports.org
Thu Sep 8 21:38:35 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 mascguy):
Replying to [comment:11 physicsbeany]:
> Hi @mascguy. sorry for missing that question.
>
> This is the only Macports install on this M1 machine, which came with
the MacOS version it's running -- Monterey. The OS has gone through a
couple of minor updates since then -- 12.4 -> 12.5 -> 12.5.1 -- but I
assume those don't require a migration of the kind you're talking about.
Okay great, that eliminates one variable from the mix. And no, a migration
is only necessary when moving to a different major version.
Thanks for confirming!
> As to your other question, I've generally been building from source
rather than prebuilt binaries.
I suppose there's nothing wrong with that, if you don't mind waiting.
(While they are very speedy, even M1 Macs take some time to churn through
complex ports like `gcc` and `libgcc`.) That being said, by building
everything from source, you're also more likely to encounter issues. So
caveat emptor!
In the interim, it looks like you don't have a full version of Xcode
installed:
{{{
debug:sysinfo Xcode none
}}}
Can you install that - using the version matching your Xcode Command-Line
Tools - and then try again? (You can identify your Xcode CLT version via
`xcodebuild -version`.)
--
Ticket URL: <https://trac.macports.org/ticket/65789#comment:12>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list