[MacPorts] #66250: libunwind: Causes other ports to fail to build

MacPorts noreply at macports.org
Sat Mar 2 19:11:21 UTC 2024


#66250: libunwind: Causes other ports to fail to build
------------------------+----------------------
  Reporter:  opencoff   |      Owner:  jeremyhu
      Type:  defect     |     Status:  assigned
  Priority:  Normal     |  Milestone:
 Component:  ports      |    Version:  2.8.0
Resolution:             |   Keywords:
      Port:  libunwind  |
------------------------+----------------------

Comment (by barracuda156):

 Replying to [comment:5 nilason]:
 > I first experienced a crash of MacPort's and System's libunwind as
 reported with #68250.
 >
 > It seems to me Xcode 15 brought changes that are causing this. With the
 {{{libunwind}}} port installed, building against libc++ the linker hooks
 up **any** binary to MacPorts' dylib making opportunistic linking for
 basically all C++ based ports. Something that will also cause crash in
 case of thrown exception. This was not the case pre-Xcode 15.
 >
 > I tend to agree with Ken, to **not** install the port {{{libunwind}}} on
 10.7+ (even though it is included in the system since 10.6:
 https://github.com/llvm/llvm-
 project/blob/main/libunwind/include/libunwind.h).
 > I also believe this is quite an urgent matter, as most problems will
 likely appear only in runtime, for potentially any C++ based ports.

 Yes, this is a problem on Sonoma, multiple ports opportunistically link to
 `libunwind`. Just one example: #68701 (but there are many more).

-- 
Ticket URL: <https://trac.macports.org/ticket/66250#comment:9>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list