This is an automated email from the ASF dual-hosted git repository.

dgkimura pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/geode-native.git


The following commit(s) were added to refs/heads/develop by this push:
     new 938581d  GEODE-3624: Add reference to boost stacktrace ticket for 
Solaris support
938581d is described below

commit 938581d811e6f6710e29940b7729b7bbc54a7e03
Author: David Kimura <[email protected]>
AuthorDate: Fri Nov 17 10:19:31 2017 -0800

    GEODE-3624: Add reference to boost stacktrace ticket for Solaris support
---
 dependencies/boost/CMakeLists.txt | 25 ++++++++++++++++---------
 1 file changed, 16 insertions(+), 9 deletions(-)

diff --git a/dependencies/boost/CMakeLists.txt 
b/dependencies/boost/CMakeLists.txt
index 5579575..30cb761 100644
--- a/dependencies/boost/CMakeLists.txt
+++ b/dependencies/boost/CMakeLists.txt
@@ -65,15 +65,22 @@ ExternalProject_Get_Property( ${${PROJECT_NAME}_EXTERN} 
INSTALL_DIR )
 set( ${PROJECT_NAME}_INSTALL_DIR ${INSTALL_DIR} )
 
 if ("SunOS" STREQUAL ${CMAKE_SYSTEM_NAME})
-set( PATCH_FILE ${CMAKE_CURRENT_SOURCE_DIR}/solaris.patch )
-ExternalProject_Add_Step( ${${PROJECT_NAME}_EXTERN} patches
-    ALWAYS 0
-    DEPENDEES download
-    DEPENDERS patch
-    DEPENDS ${PATCH_FILE}
-    WORKING_DIRECTORY ${${PROJECT_NAME}_SOURCE_DIR}
-    COMMAND ${PATCH} -u -N -p1 < ${PATCH_FILE}
-)
+  #
+  # Solaris patch is to workaround issue of dladdr function signature
+  # mismatching the signature boost stacktrace expects. Following boost ticket
+  # tracks this issue:
+  #
+  #     https://svn.boost.org/trac10/ticket/13300#ticket
+  #
+  set( PATCH_FILE ${CMAKE_CURRENT_SOURCE_DIR}/solaris.patch )
+  ExternalProject_Add_Step( ${${PROJECT_NAME}_EXTERN} patches
+      ALWAYS 0
+      DEPENDEES download
+      DEPENDERS patch
+      DEPENDS ${PATCH_FILE}
+      WORKING_DIRECTORY ${${PROJECT_NAME}_SOURCE_DIR}
+      COMMAND ${PATCH} -u -N -p1 < ${PATCH_FILE}
+  )
 endif()
 
 add_library(${PROJECT_NAME} INTERFACE)

-- 
To stop receiving notification emails like this one, please contact
['"[email protected]" <[email protected]>'].

Reply via email to