Details
-
Bug
-
Resolution: Out of scope
-
Not Evaluated
-
None
-
5.15.9
-
None
-
Mac OS 12.2, Xcode 13.3, Qt 5.15.9
Description
Since Qt 5.15.9 came out with universal binary support I have rushed in updating my applications by popular customer demand. However, after deploying it to production it seems that it is breaking Mac OS 10.13 support.
Attached are two crash logs from a customer who is running one of our apps in Mac OS 10.13.
Both seems to break on the QNetworkAccessManager in a point that seems to be doing ssl stuff. OpenSSL version is 1.1.1m. This was the OpenSSL version I was already using with Qt 5.15.8 and apparently there was no issue. I have compiled Qt 5.15.9 with openssl-linked support in the following way:
./configure -confirm-license -recheck -prefix /Users/nsantos/Qt/5.15.9/clang_64_static -platform macx-clang -device-option QMAKE_APPLE_DEVICE_ARCHS="x86_64 arm64" -commercial -debug-and-release -static -nomake examples -nomake tests -opengl desktop -no-securetransport -openssl-linked -I/usr/local/Cellar/openssl@1.1/1.1.1m/include OPENSSL_LIBS="/usr/local/Cellar/openssl@1.1/1.1.1m/lib/libssl.a /usr/local/Cellar/openssl@1.1/1.1.1m/lib/libcrypto.a" -qtnamespace com_imaginando_qt_5_15_9
Note: openssl1.1.1m was installed via macbrew on a Intel Mac and on a Apple Silicon Mac and merged toghether as a fat lib using lippo. I'm linking with the fat libs.