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
Searching around online, people on Stack Overflow seem to think that
'unknown file type: first eight bytes' indicates that it's because the
'.dylib' file is actually an ELF shared object format (i.e. a Linux-style
'.so' file), instead of a Mach-O binary format. A.I. sources seem to think
that either it's the ELF/Mach-O reason, or that the file is corrupted or an
empty file, based on the fact that dyld is seeing all zeros for the first
eight bytes.
Has anyone else ever seen a similar error? Is it possible there could be
something wrong with the current openssl3 port?
--
Jason Liu
