kszucs edited a comment on pull request #10659: URL: https://github.com/apache/arrow/pull/10659#issuecomment-879866046
> These only seem to be warnings and not errors. Hard to determine if they really are problematic without seeing the full linker line as that could simply contain both static libraries. It would work if it is always ignoring one of them. @xhochy what do you mean under both libraries? The vcpkg dependencies are built as universal2 binaries. After inspecting the rest of the dependencies seems like libcrypto and libssl are the only ones built as arm64 only libraries: ```console ursa-m1-mini:lib github$ file libz.a libz.a: Mach-O universal binary with 2 architectures: [x86_64:current ar archive random library] [arm64:current ar archive random library] libz.a (for architecture x86_64): current ar archive random library libz.a (for architecture arm64): current ar archive random library ``` ```console ursa-m1-mini:lib github$ file libssl.a libssl.a: current ar archive random library ursa-m1-mini:lib github$ file libcrypto.a libcrypto.a: current ar archive random library ``` ```console ursa-m1-mini:lib github$ lipo -info libz.a Architectures in the fat file: libz.a are: x86_64 arm64 ursa-m1-mini:lib github$ lipo -info libssl.a Non-fat file: libssl.a is architecture: arm64 ``` If the linker just ignores these libraries then I assume that there should be missing symbols in the final libarrow binary, but the tests don't trigger such an error. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
