The reason your build fails is this: It uses the headers from ports, but links against the version shipped with OSX (they still have one, just don't ship the headers) which is a 0.9.x version if I recall correctly.
Change the path of the lib to /opt/local/lib/libcrypto.dylib (and libssl.dylib) and everyghing should work. regards Armin On 05/16/2018 03:55 PM, Vladimir via FreeRDP-devel wrote: > Armin, thanks for reply, here are these values: > > //Path to a library. > OPENSSL_CRYPTO_LIBRARY:FILEPATH=/usr/lib/libcrypto.dylib > > //Path to a file. > OPENSSL_INCLUDE_DIR:PATH=/opt/local/include > > //Path to a library. > OPENSSL_SSL_LIBRARY:FILEPATH=/usr/lib/libssl.dylib > > libcrypto.dylib and libssl.dylib are links, pointing to : > /usr/lib/libcrypto.35.dylib > /usr/lib/libssl.35.dylib > > Some values from printenv: > OPENSSL_INCLUDE_DIR=/opt/local/include > PATH=/opt/local/bin:/opt/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/CMake.app/Contents/bin > > LC_CTYPE=UTF-8 > > header files in /opt/local/includewas created by macports, so there is > an openssl folder with headers, lines from opensslv.h from here: > --------------- > # define OPENSSL_VERSION_NUMBER 0x100020ffL > # ifdef OPENSSL_FIPS > # define OPENSSL_VERSION_TEXT "OpenSSL 1.0.2o-fips 27 Mar 2018" > # else > # define OPENSSL_VERSION_TEXT "OpenSSL 1.0.2o 27 Mar 2018" > # endif > # define OPENSSL_VERSION_PTEXT " part of " OPENSSL_VERSION_TEXT > > # define SHLIB_VERSION_HISTORY "" > # define SHLIB_VERSION_NUMBER "1.0.0" > --------------------- > > error is: > [ 38%] Building C object > winpr/libwinpr/CMakeFiles/winpr.dir/clipboard/synthetic.c.o > [ 38%] Building C object > winpr/libwinpr/CMakeFiles/winpr.dir/clipboard/clipboard.c.o > [ 39%] Building C object > winpr/libwinpr/CMakeFiles/winpr.dir/clipboard/posix.c.o > [ 39%] Linking C shared library libwinpr2.dylib > Undefined symbols for architecture x86_64: > "_FIPS_mode", referenced from: > __winpr_openssl_initialize in ssl.c.o > _winpr_FIPSMode in ssl.c.o > "_FIPS_mode_set", referenced from: > __winpr_openssl_initialize in ssl.c.o > ld: symbol(s) not found for architecture x86_64 > clang: error: linker command failed with exit code 1 (use -v to see > invocation) > make[2]: *** [winpr/libwinpr/libwinpr2.2.0.0.dylib] Error 1 > make[1]: *** [winpr/libwinpr/CMakeFiles/winpr.dir/all] Error 2 > make: *** [all] Error 2 > > Any suggestion? > > P.S. > New in this mailing list. Should I just reply to > freerdp-devel@lists.sourceforge.net or should I additionally keep > other's email in CC, or vice-versa? > > On 16.05.2018 15:42, Armin Novak via FreeRDP-devel wrote: >> Hi Vladimir, FreeRDP does not access FIPS related functions of >> OpenSSL. It first checks with a call to FIPS_mode (which is available >> from version 1.0.1) if it is enabled. If your compile is failing, best >> check which version is detected and if the includes match the library >> found. (Both can be found in the CMakeCache.txt file generated, >> OPENSSL_INCLUDE_DIR and OPENSSL_SSL_LIBRARY) best Armin On 05/16/2018 >> 10:17 AM, Vladimir via FreeRDP-devel wrote: >>> Greetings to all! I was trying to compile xFreeRdp on macOS following >>> the instructions here >>> https://github.com/FreeRDP/FreeRDP/wiki/Compilation and have >>> problems. Apple don't provide openssl on Mac anymore, and so we need >>> to install it from brew or from macports. But! Currently FreeRDP >>> tries to access "FIPS" extensions in openssl when on linking stage, >>> and as I can say after some research - nor homebrew nor macports >>> provides opeenssl with FIPS extensions, just openssl without FIPS. >>> Even more, I was reading that openssl project don't recommend/provide >>> to enable/compile FIPS on macOS system - in their PDF document macOS >>> was not in list of systems that could use FIPS. (Sorry for not exact >>> terms, I don't understand the details yet, just common things >>> regarding this FIPS and openssl on mac) So, could you recommend the >>> workaround for this situation? Can I somehow disable using of "FIPS" >>> in FreeRDP so "usual" openssl could be used to build? If so, will >>> that break some compatibility with Microsoft RDP server on Windows? >>> If we really need FIPS in FreeRDP but openssl don't >>> provide/recommed/etc FIPS on macOS platform - what we can do? I saw >>> that you are trying to create/use your own encryption layer which >>> will internally use different "backends" like openssl or other >>> system. Is there any progress in using Apples's native encryption >>> libs instead of openssl on mac(& ios?) platform? I assume this will >>> be a real "solution" for the issue. Any starting point to look at >>> this? I appreciate any comment on this or even simple link to help me >>> move forward on this problem. Vladimir. >>> ------------------------------------------------------------------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>> _______________________________________________ FreeRDP-devel mailing >>> list FreeRDP-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/freerdp-devel >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ FreeRDP-devel mailing >> list FreeRDP-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/freerdp-devel > > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > FreeRDP-devel mailing list > FreeRDP-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/freerdp-devel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ FreeRDP-devel mailing list FreeRDP-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freerdp-devel
