Strange curl4/openssl3 error messages when building a local port

Fred Wright fw at fwright.net
Sat Dec 13 19:50:42 UTC 2025


On Sat, 13 Dec 2025, Dave Allured - NOAA Affiliate via macports-dev wrote:

> I spot checked the latest pre-built binaries at
> https://packages.macports.org/openssl3/.  The first four bytes should be
> "cf fa ed fe" for both ARM and X86 macs.  Manually check your
> /opt/local/libexec/openssl3/lib/libssl.3.dylib with "od -tx1 -N16" to
> ensure that your configure process was not confused, but it is probably not.
>
> So yes, it looks like that libssl.3.dylib file is broken.  I don't know how
> that might have happened, but I wonder why.  Try reinstalling the openssl3
> port.

Before that, you might just try deactivating and activating it, in case it 
was just a spaz in the activate extraction (or post-activate clobberage).

Fred Wright

> On Sat, Dec 13, 2025 at 10:40 AM Jason Liu <jasonliu at umich.edu> wrote:
>
>> Hi all,
>>
>> I'm trying to build a port locally on my machine, and this port depends on
>> curl/openssl3. During the build, I am getting some error messages that
>> baffle me. At the configure stage, the build is giving the following:
>>
>> dyld: Library not loaded: /opt/local/libexec/openssl3/lib/libssl.3.dylib
>>   Referenced from: /opt/local/lib/libcurl.4.dylib
>>   Reason: no suitable image found.  Did find:
>>         /opt/local/libexec/openssl3/lib/libssl.3.dylib: unknown file type,
>> first eight bytes: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
>>         /opt/local/libexec/openssl3/lib/libssl.3.dylib: stat() failed with
>> errno=1
>>         /opt/local/libexec/openssl3/lib/libssl.3.dylib: unknown file type,
>> first eight bytes: 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
[...]


More information about the macports-dev mailing list