I thought that bug was related to SIP, but it doesn't seem to be. That's what I get for skimming.
I'm trying on 13, 14 VMs and saw the extract bug, and figured I could get around it by disabling SIP, but it looks like its codesigning. I might give it a try anyway. csrutil disable turns off a lot of stuff, and on a fresh VM with just Xcode and macports, I don't care, unlike on my actual machine where I keep SIP on for obvious reasons. Maybe I just need to dig up an intel mac. I might have one around here someplace. —Mark On Fri, Oct 4, 2024, at 6:14 PM, Ryan Carsten Schmidt wrote: > > On Oct 4, 2024, at 15:57, Mark E Anderson wrote: >> >> Because I refuse to let qt5-qtwebengine beat me, I've been running macports >> in VMs to test what the heck is going on with patching ninja files. Trace >> mode will work better if I turn SIP off, correct? But if I do, will things >> succeed that should fail? Or should I worry about that later, since they'll >> get tested on the build bot and CI? > > Trace mode fails to work on macOS 13 and later on Apple Silicon processors. A > solution has been suggested here: > > #66358 (sip-workaround / trace mode no longer works on arm64 macOS ≥ 13 due > to new security features) <https://trac.macports.org/ticket/66358#comment:58> > trac.macports.org <https://trac.macports.org/ticket/66358#comment:58> > macports.ico <https://trac.macports.org/ticket/66358#comment:58> > > Trace mode works fine on all macOS versions on Intel processors. > > I don't know the consequences of turning off SIP. It's not recommended but > probably fine in your case if you want to try it? I'm not sure why it would > help though.
