build failure on Mac Pro with Apple M2 Chip.

[tpa10]

Describe the bug
ld emits warning:
ld: warning: ignoring file /Users/tpa/oqs-provider-git-repo/oqs-provider/.local/lib/libcrypto.dylib, building for macOS-x86_64 but attempting to link with file built for macOS-arm64
and subsequent link step fails due to not finding entry points...

Undefined symbols for architecture x86_64:
"_ASN1_item_d2i_ex", referenced from:
_oqsx_d2i_X509_PUBKEY_INTERNAL in oqs_decode_der2key.c.o
"_ERR_new", referenced from:
_OSSL_provider_init in oqsprov.c.o
_oqsx_key_op in oqsprov_keys.c.o
_oqsx_key_new in oqsprov_keys.c.o
_oqsx_key_fromdata in oqsprov_keys.c.o
_oqsx_key_recreate_classickey in oqsprov_keys.c.o
_oqsx_key_new_from_nid in oqsprov_keys.c.o
_oqsx_import in oqs_kmgmt.c.o
...
etc, etc.

To Reproduce
Steps to reproduce the behavior:

1. git clone https://github.com/open-quantum-safe/oqs-provider.git
2. cd ors-provider
3. scripts/fullbuild.sh -F

Expected behavior
Expected build to complete without error.

Screenshots
If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

• OS: MacOS Ventura 13.3.1
• OpenSSL version: OpenSSL 3.2.0-dev (Library: OpenSSL 3.2.0-dev )
• Version [e.g. 0.4.0]

Additional context
it appears that openssl is being built for arm64 and oqs-provider is trying to build for X86_64, but I have no idea how to fix this.
note that I get the same result, whether I use the "fullbuild.sh" script, or if I manually build & install openssl and liboqs.
Those components build and run, but when I attempt to use them to build oqs-provider, I get the arch mismatch problem.
I expect this is NOT an issue on an older Mac that is using an intel chip.

[baentsch]

Thanks for this report. It's puzzling indeed and I have no M2 to test this on. Build on M1 following the 3 steps outlined above works without problems. Also there is no reference to "x64" anywhere in the code of oqsprovider.

So the best thing I can offer is to review the output of your cmake run: Please share everything output by fullbuild.sh: Maybe there's a wrong compiler setting visible somewhere... In addition, can I ask you to run make run_tests in the liboqs/_build subdirectory created as part of the oqsprovider build? This just to test that cmake works OK for liboqs.

[dstebila]

I just compiled on my M2 with macOS 13.4.1 and did not get any errors. I wonder if it has something to do with the OpenSSL version. How did you install OpenSSL 3.2.0-dev? For me, cmake finds OpenSSL 1.1.1u via brew. I do have OpenSSL 3.1.1 installed via brew but the build scripts apparently find the 1.1.1 installation.

[tpa10]

Thank you for following up. I will go back and re-check my steps from OpenSSL install/build, liboqs install/build (making sure to run the “test” target), and the oqs-provider build and let you know.

…

On Wed, Jul 5, 2023 at 6:40 PM Douglas Stebila ***@***.***> wrote: I just compiled on my M2 with macOS 13.4.1 and did not get any errors. I wonder if it has something to do with the OpenSSL version. How did you install OpenSSL 3.2.0-dev? For me, cmake finds OpenSSL 1.1.1u via brew. I do have OpenSSL 3.1.1 installed via brew but the build scripts apparently find the 1.1.1 installation. — Reply to this email directly, view it on GitHub <#199 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA6WIS65CTZFGT4QQFVYRVTXOYJPPANCNFSM6AAAAAAZWRUSUM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[baentsch]

but the build scripts apparently find the 1.1.1 installation.

This should be fixed by now courtesy #212.

@tpa10 , please retry with latest code.

[tpa10]

Will do, thanks!

…

On Fri, Jul 14, 2023 at 2:22 AM Michael Baentsch ***@***.***> wrote: but the build scripts apparently find the 1.1.1 installation. This should be fixed by now courtesy #212 <#212>. @tpa <https://github.com/tpa>, please retry with latest code. — Reply to this email directly, view it on GitHub <#199 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA6WIS3PGLHBPWK4OXRCSR3XQEFVBANCNFSM6AAAAAAZWRUSUM> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[baentsch]

Closing assuming this is fixed. Please re-open if not, providing new logs.