You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ld: warning: ignoring file /Users/markqian/licode/build/libdeps/build/lib/libcrypto.dylib, building for macOS-arm64 but attempting to link with file built for macOS-x86_64
Undefined symbols for architecture arm64:
"_EVP_EncryptInit", referenced from:
_main in conftest-72da8e.o
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
...
configure:5418: error: in `/Users/markqian/licode/build/libdeps/libsrtp-2.1.0':
configure:5420: error: can't find openssl >= 1.0.1 crypto lib
when building on mac mini which uses m1 chip. Is there a way to resolve this?
Steps to reproduce the issue:
clone repo
run install script for mac
Describe the results you received:
ld: warning: ignoring file /Users/markqian/licode/build/libdeps/build/lib/libcrypto.dylib, building for macOS-arm64 but attempting to link with file built for macOS-x86_64
Undefined symbols for architecture arm64:
"_EVP_EncryptInit", referenced from:
_main in conftest-72da8e.o
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
...
configure:5418: error: in `/Users/markqian/licode/build/libdeps/libsrtp-2.1.0':
configure:5420: error: can't find openssl >= 1.0.1 crypto lib
Describe the results you expected:
Build successfully
Additional information you deem important (e.g. issue happens only occasionally):
Licode commit/release where the issue is happening
Description
I am getting build failure
when building on mac mini which uses m1 chip. Is there a way to resolve this?
Steps to reproduce the issue:
Describe the results you received:
Describe the results you expected:
Build successfully
Additional information you deem important (e.g. issue happens only occasionally):
Licode commit/release where the issue is happening
Additional environment details (Local, AWS, Docker, etc.):
The text was updated successfully, but these errors were encountered: