Re: [deal.II] Regarding using Boost library functions with deal.II

2021-05-14 Thread Bruno Turcksin
Kishore, In detailed.log you should be able see which version of Boost has been picked up by deal.II. In your case you want to make sure that you are not using the bundled version of Boost. The reason is that the bundled Boost does not include all of Boost but only a subset of it. Best, Bruno

Re: [deal.II] Regarding using Boost library functions with deal.II

2021-05-14 Thread Kishore Nori
I have isolated the error to minimum (not-) working example: The error occurs when Point and Boost functions are used at once in a dealii program. I have observed that in the Point class there is usage of some boost functions, could it be that there is clash with that boost version and the

Re: [deal.II] Regarding using Boost library functions with deal.II

2021-05-14 Thread Kishore Nori
Dear Prof. Bangerth, Thank you for the reply, yes I was having some doubt on this. I removed the FIND_PACKAGE(Boost REQUIRED) in CMakeLists.txt but I still get the error. Could it be because of the boost include file? #include Does deal.II come with boost library included? If yes, how can I

Re: [deal.II] Regarding using Boost library functions with deal.II

2021-05-14 Thread Wolfgang Bangerth
On 5/14/21 8:17 AM, Bruno Turcksin wrote: Can you show the result of the command ldd, i.e. what do you see when you type ldd ./my_code Could it be that you are linking against both the version of BOOST that comes with deal.II and against an external one? That would explain why things

Re: [deal.II] Regarding using Boost library functions with deal.II

2021-05-14 Thread Kishore Nori
Dear Bruno, Thank you very much for the great lead. I have already included the specific .hpp file, in this case #include in the main file, and the function I use is in this .hpp file, which works fine when I run the same function without deal.II in sample cpp file. I am using the simple

Re: [deal.II] Regarding using Boost library functions with deal.II

2021-05-14 Thread Bruno Turcksin
Kisher, According to https://www.boost.org/doc/libs/1_76_0/more/getting_started/unix-variants.html#header-only-libraries has functions that require the package to be compiled. However, I don't see libboost_math.so.1.71.0 when you do ldd. So it looks like you forgot to add math as a component in

Re: [deal.II] Regarding using Boost library functions with deal.II

2021-05-14 Thread Kishore Nori
Dear Bruno, Thank you for the reply :) The following is the result of ldd ./executable: linux-vdso.so.1 (0x7ffd36c7c000) libdeal.ii.g.so.9.2.0 => /lib/x86_64-linux-gnu/libdeal.ii.g.so.9.2.0 (0x7f0ac6662000) libtrilinos_teuchoscomm.so.12 =>

Re: [deal.II] Regarding using Boost library functions with deal.II

2021-05-14 Thread Bruno Turcksin
Kishore, Can you show the result of the command ldd, i.e. what do you see when you type ldd ./my_code Best, Bruno On Friday, May 14, 2021 at 9:32:26 AM UTC-4 kishore...@gmail.com wrote: > Just an update: The code gives the above errors even before the execution > of the code starts. The

Re: [deal.II] Regarding using Boost library functions with deal.II

2021-05-14 Thread Kishore Nori
Just an update: The code gives the above errors even before the execution of the code starts. The compilation (using make) doesn't give any errors, and when run the executable using make run, these errors are displayed. On Thursday, May 13, 2021 at 10:36:32 PM UTC+5:30 Kishore Nori wrote: >

Re: [deal.II] Regarding using Boost library functions with deal.II

2021-05-13 Thread Kishore Nori
Sorry that didn't mention more details: I am running deal.II 9.2.0 on Ubuntu 20.04, installed through the available PPA. The only boost function I am using is spherical_harmonic_r(l, m, theta, phi) inside a simple user-defined function which returns the spherical harmonic value times a const.

Re: [deal.II] Regarding using Boost library functions with deal.II

2021-05-13 Thread Wolfgang Bangerth
On 5/13/21 8:56 AM, Kishore Nori wrote: I would be very happy to know on why the problem is arising and how can I fix it? We don't know without being able to see what specifically your code looks like and the system it is running on -- but the way to find out is to run your program in a