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
In a cross-build environment I noticed that that the CMake build for plugins/message-timestamp with TLS enabled is currently broken because opensslconf.h cannot be found. Note the header is only missing for this specific target.
I had a cursory look at the CMake file and it seems that plugins/message-timestamp/CMakeLists.txt is not adding ${OPENSSL_INCLUDE_DIRECTORIES} to to the include directories. opensslconf.h is transitively included by config.h
This does not seem to be an issue in a non-cross build because because /usr/include and /usr/local/include are part of the default include paths. This is not the case when using a cross compiler.
Additionally this seems to be a regression between 1.6.x and 2.0.x as I discovered this during an upgrade from 1.6 to 2.0 in the same build environment.
Edit:spelling
The text was updated successfully, but these errors were encountered:
Ozaq
changed the title
CMake build for plugins/message-timestamp cannot find opensslconf.h
CMake build for plugins/message-timestamp cannot find opensslconf.h with cross-compiler
Mar 30, 2021
In a cross-build environment I noticed that that the CMake build for plugins/message-timestamp with TLS enabled is currently broken because opensslconf.h cannot be found. Note the header is only missing for this specific target.
I had a cursory look at the CMake file and it seems that
plugins/message-timestamp/CMakeLists.txt
is not adding${OPENSSL_INCLUDE_DIRECTORIES}
to to the include directories.opensslconf.h
is transitively included byconfig.h
This does not seem to be an issue in a non-cross build because because
/usr/include
and/usr/local/include
are part of the default include paths. This is not the case when using a cross compiler.Additionally this seems to be a regression between 1.6.x and 2.0.x as I discovered this during an upgrade from 1.6 to 2.0 in the same build environment.
Edit:spelling
The text was updated successfully, but these errors were encountered: