[MacPorts] #62769: iTerm2 @ 3.4.6: Embedded iTermServer binary linked against ubsan

MacPorts noreply at macports.org
Wed Apr 28 06:47:24 UTC 2021


#62769: iTerm2 @ 3.4.6: Embedded iTermServer binary linked against ubsan
----------------------+--------------------
 Reporter:  gnachman  |      Owner:  (none)
     Type:  defect    |     Status:  new
 Priority:  Normal    |  Milestone:
Component:  ports     |    Version:  2.6.4
 Keywords:            |       Port:  iTerm2
----------------------+--------------------
 Please see this issue for the original user reports:
 https://gitlab.com/gnachman/iterm2/-/issues/9637

 I can reproduce this:
 1. On macOS 10.15.7, run `sudo port install iTerm2`
 2. Run `otool -L` on `iTerm.app/Contents/MacOS/iTermServer` and see that
 `ubsan` is among the required dynamic libraries.

 I don't know why that is the case—perhaps MacPorts is building against a
 target other than Deployment? The Development target does have this
 enabled, but that isn't intended to be used by end users. Deployment is
 meant for end users. If you need different settings, like disabling
 signing, I could possibly add a new build target.

 I am not the port maintainer, just the app author and I'd like to get
 people up and running again.

 This bug is particularly painful for users because the broken iTermServer
 binary is cached and won't be overwritten until they to go a new version.
 Users will need to manually delete `~/Library/Application
 Support/iTerm2/iTermServer-3.4.6` and then install a working build in
 order to recover.

 I'm open to suggestions on how to prevent such problems in the future!

-- 
Ticket URL: <https://trac.macports.org/ticket/62769>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list