Strange curl4/openssl3 error messages when building a local port

[Ryan Carsten Schmidt]

On Dec 13, 2025, at 11:40, Jason Liu wrote:
> 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

If it starts with zeroes, it's not a dylib, so it's corrupted. 

This could be a symptom of the filesystem cache bug we've encountered before; unexpected chunks of zeroes in a file is the symptom. 

https://trac.macports.org/ticket/67336

Workarounds for this bug are in MacPorts 2.10.3 and later. So if it is the cause of the problem for you, either you installed the port with an earlier MacPorts version, or you received an archive from our server that was built with an earlier version, or there are additional expressions of the bug that we don't know about and haven't worked around yet. 

To discover when you installed the port, run:

port -v installed $(port -q provides /opt/local/libexec/openssl3/lib/libssl.3.dylib)

Deactivating and reactivating the port is a good idea. If that doesn't solve the problem, try reinstalling it:

sudo port -n upgrade --force $(port -q provides /opt/local/libexec/openssl3/lib/libssl.3.dylib)

If that doesn't work, we can check if the problem is in the archives on the server. 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20251213/6b1dd0f0/attachment.htm>