During Migration to Arm64 mac, should I null out archs='x86_64' from installed ports list?

Daniel J. Luke dluke at geeklair.net
Thu Apr 14 19:34:29 UTC 2022

On Apr 14, 2022, at 2:56 PM, Peter Serocka <peserocka at gmail.com> wrote:
>> On Apr 14, 2022, at 14:10, chilli.namesake at gmail.com wrote:
> Xcode version mismatch issues do exist in some situations, and I have been dealing with those; but my point here is that the port command itself refuses to do any further work after a major macOS upgrade. It chokes quite early, inside proc mportinit found in <prefix>/libexec/macports/lib/macports1.0/macports.tclmacports.tcl
> and the error message is:
> Error: Current platform "darwin 19" does not match expected platform "darwin 18"
> Error: If you upgraded your OS, please follow the migration instructions: https://trac.macports.org/wiki/Migration
> OS platform mismatch
>    while executing
> "mportinit ui_options global_options global_variations"
> Error: /opt/macports18/bin/port: Failed to initialize MacPorts, OS platform mismatch
> Which prevents further upgrades or installs in the existing tree. 

... until you follow the instructions.

Once you do step 2, the port command works again (and you should follow the rest of the instructions, but if you're prepared to live with the consequences of things maybe breaking because you didn't follow good advice, even things like 'port install' and 'port upgrade outdated' mostly work at that point).

Daniel J. Luke

More information about the macports-users mailing list