Thanks for the suggestion. I have been on Catalina for 4 months. It is possible
that my employer upgraded something that I did not know about with their
access. I will check SDK.
Sent from my iPhone
++Eric
> On Apr 25, 2021, at 20:58, Joshua Root <[email protected]> wrote:
>
> Fielding, Eric J wrote:
>> I was running a `port upgrade outdated` (actually I had to add `and not
>> py37-scipy` as that was not building), and when it finished upgrading ports,
>> it started the usual “Scanning binaries for linking errors”. This step is
>> crashing with a “Segmentation fault” after about 30%. Does this mean my
>> ports database is corrupted or something like that? Is there a way to
>> recover without reinstalling all the ports? I am running “MacPorts base
>> version 2.6.4” on Catalina.
>
> This happens if you build MacPorts base against the macOS 11 SDK and run it
> on an older OS version. Ticket:
> <https://urldefense.us/v3/__https://trac.macports.org/ticket/61540__;!!PvBDto6Hs4WbVuu7!Y-iWfhpVzQY8dRWr984mW3Z4frsQXiWPcqEyL4e-8B3T2E3Kph8_64R7AeDkk1cEGK9SNs0PQw$
> >
>
> Only the rev-upgrade operation is affected; your ports are correctly upgraded
> before the crash happens. Installing from the binary .pkg or building against
> the 10.15 SDK will avoid the problem.
>
> - Josh
