Hi, I've been reviewing geode-native headers and there is no boost code exposed there. Also, as can be observed here: https://github.com/apache/geode-native/blob/26fe7275cce96b5a3ea785e38f340c9c9c6773d5/dependencies/boost/CMakeLists.txt#L35, Boost is statically linked to geode-library. [https://opengraph.githubassets.com/3bd989ea7a80472c63a535297986dbd6833608a54b7fde59d546b21e45d10ec2/apache/geode-native]<https://github.com/apache/geode-native/blob/26fe7275cce96b5a3ea785e38f340c9c9c6773d5/dependencies/boost/CMakeLists.txt#L35> geode-native/CMakeLists.txt at 26fe7275cce96b5a3ea785e38f340c9c9c6773d5 ยท apache/geode-native<https://github.com/apache/geode-native/blob/26fe7275cce96b5a3ea785e38f340c9c9c6773d5/dependencies/boost/CMakeLists.txt#L35> Apache Geode Native. Contribute to apache/geode-native development by creating an account on GitHub. github.com So, the only problematic scenario in terms of Boost linking conflicts would be if you are using the same building environment for your application and for Geode. My guess here is that it could happen that Boost headers from your environment (at 1.78.0 apparently) are used to compile Geode-Native, instead of the ones downloaded in the dependencies (1.76.0) and I suppose that 1.76.0 and 1.78.0 have API compatible changes, but breaking ones in term of ABI, thus causing the coredump.
Usually, in order to compile Geode Native I use one of the Docker images<https://github.com/apache/geode-native/tree/develop/docker> already included in the repository, to avoid dependency issues. If my guess is still not correct I'd encourage you to open a Jira case, so the issue can be tackled by the community. Regarding plans to uplift to 1.78.0 or later, there is currently an open PR by Michael Oleske (PR #967<http://PR%20#967>) to uplift to 1.79, it just requires some care to Windows plat, so I guess it shouldn't take long... BR /Mario ________________________________ From: Wei Yi Luo <weiyi....@est.tech> Sent: Monday, July 11, 2022 7:03 AM To: user@geode.apache.org <user@geode.apache.org> Cc: d...@geode.apache.org <d...@geode.apache.org> Subject: Questions regarding boost version of native client Hi all, When trying to use a recent boost 1.78.0 library (dynamically loaded by application process), core file was triggered by native client library during pool creation. Her comes the questions: 1. Is it recommended to tweak boost version by application and how risky it could be? 2. 3. Any plan when to uplift boost version towards 1.78.0 or later? Thanks! Br Bo
