[MacPorts] #69873: Potential signing issue with libiconv
MacPorts
noreply at macports.org
Tue Apr 30 12:48:56 UTC 2024
#69873: Potential signing issue with libiconv
---------------------+--------------------
Reporter: Gandoon | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Keywords: | Port:
---------------------+--------------------
This is essentially a follow-up to the now closed ticket #67359.
Originally I had some problems building the new Transmission 4, but I had
a weird libxml2 error that kept bugging me. That was indeed solved as it
seemed to be down to a stale modulemap on my system that frustrated the
build.
However, despite a subsequent successful build then a new problem arose:
The application crashes immediately with a dyld error message:
{{{
Process: Transmission [14814]
Path:
/Applications/MacPorts/Transmission.app/Contents/MacOS/Transmission
Identifier: org.m0k.transmission
Version: 4.0.5 (14714.4.0.5)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Transmission [14814]
User ID: 502
Date/Time: 2024-04-30 14:23:55.259 +0200
OS Version: Mac OS X 10.15.7 (19H2026)
Report Version: 12
Anonymous UUID: * * *
Time Awake Since Boot: 12000 seconds
System Integrity Protection: enabled
Crashed Thread: 0
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Reason: DYLD, [0x5] Code Signature
Application Specific Information:
dyld: launch, loading dependent libraries
Dyld Error Message:
Library not loaded: /opt/local/lib/libiconv.2.dylib
Referenced from:
/Applications/MacPorts/Transmission.app/Contents/MacOS/Transmission
Reason: no suitable image found. Did find:
/opt/local/lib/libiconv.2.dylib: code signature in
(/opt/local/lib/libiconv.2.dylib) not valid for use in process using
Library Validation: mapped file has no cdhash, completely unsigned? Code
has to be at least ad-hoc signed.
/opt/local/lib/libiconv.2.dylib: stat() failed with errno=1
.
.
.
}}}
There is no problem when building Transmission with code directly from the
GitHub repository, so I am suspecting there may be something funny going
on with MacPorts' `libiconv`. As suggested in #67359, I start this new
ticket for the `libiconv` issue, in case this is something that should and
can be fixed on the MacPorts side.
--
Ticket URL: <https://trac.macports.org/ticket/69873>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list