-
Notifications
You must be signed in to change notification settings - Fork 201
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compiling fails on m1 (MacOS Ventura 13.1) #242
Comments
You need to supply the same flags as you did for OpenSSL. In your case it seems that |
Sorry for being dense but I don't see how to apply your suggestion. I tried passing it before the "make osx" command line as ENV variables but nothing really changed. I see that some CFLAGS are hardcoded in the Makefile.am and I tried changing it there too, but again it did not improve things much. I guess my question really was about the support status of vsmartcard on arm macs. Also, would it be possible to provide binaries for macos too as it's done for Windows? Thanks a lot for your patience.. |
OpenSSL prints the compiler flags when configuring it. What is shown as result of ./config for you? If you're using some binary of, say homebrew, you may want to check their build script... |
From what I can see (I checked the config and the Configure files under openssl) the bundled OpenSSL is from 2019 and it has support for stuff like linux-aarch64 and android but not macos... Maybe support for apple silicon has been added later .. |
Hi, same for me. Steps for reproduce:
Without using homebrews pcsc-lite, configure phase fails as described in #248
The result however is:
Is there any other way, how to pass CFLAGS & LDFLAGS ? Thanks. |
Hi Frank, Same reproduced in my MacOS Ventura. According to OpenSSL 1.0.2 docs, it does not allow building for arm64 architecture and falls back to i386.
It says it can't find the header files normally symlinked to |
A lot of hardcoded x86_64 architecture... I'm not sure all steps are required, but here they are:
|
for now, don't hassle with creating fat ssl binaries by using lipo. just remove openpace from the binaries for now. fixes #242
for now, don't hassle with creating fat ssl binaries by using lipo. just remove openpace from the binaries for now. fixes #242
thanks for the hint. for now, I've disabled linking against openssl (and openpace) to avoid fiddeling around with lipo to create fat binaries (for arm and intel). |
Expected behaviour
Compiling the sources using the instructions provided for MacOS would result in a compiled package
Actual behaviour
Plenty of errors during linking. I think that arm64 on macos is completely unsupported (I see plenty of messages mentioning -arch i386 and/or -arch x86_64 in the output)
Steps to reproduce
Logs
Some lines from the log:
"_vfprintf", referenced from:
_OPENSSL_showfatal in libcrypto.a(cryptlib.o)
"_write$UNIX2003", referenced from:
_raw_write_stdout in apps.o
_conn_write in libcrypto.a(bss_conn.o)
_conn_puts in libcrypto.a(bss_conn.o)
_dgram_write in libcrypto.a(bss_dgram.o)
_fd_write in libcrypto.a(bss_fd.o)
_sock_write in libcrypto.a(bss_sock.o)
_RAND_query_egd_bytes in libcrypto.a(rand_egd.o)
...
ld: symbol(s) not found for architecture i386
clang: error: linker command failed with exit code 1 (use -v to see invocation)
The text was updated successfully, but these errors were encountered: