> About `db_berkeley` error. On rpm-based systems presents two Berkley-related 
> devel packages
> 
> ```
> libdb-devel
> libdb-cxx-devel
> ```
> 
> in this files present this devel files
> 
> ```
> [root@nout SPECS]# rpm -ql libdb-devel
> /usr/include/db.h
> /usr/include/db_185.h
> /usr/include/libdb
> /usr/include/libdb/db.h
> /usr/include/libdb/db_185.h
> /usr/lib64/libdb.so
> [root@nout SPECS]# rpm -ql libdb-cxx-devel
> /usr/include/db_cxx.h
> /usr/include/libdb/db_cxx.h
> /usr/lib64/libdb_cxx.so
> ```
> 
> For Kamailio build required 'C' version devel files. But cmake file used 
> `C++` version. Could you make change like
> 
> ```diff
> diff --git a/cmake/modules/FindBerkeleyDB.cmake 
> b/cmake/modules/FindBerkeleyDB.cmake
> index d625ff410f..423230ff2e 100644
> --- a/cmake/modules/FindBerkeleyDB.cmake
> +++ b/cmake/modules/FindBerkeleyDB.cmake
> @@ -45,7 +45,7 @@ endif()
>  
>  find_path(
>    BerkeleyDB_INCLUDE_DIR
> -  NAMES db_cxx.h
> +  NAMES db.h
>    HINTS ${_BerkeleyDB_homebrew_prefix}/include
>    PATH_SUFFIXES
>      4.8
> ```
> 
> Similar devel files are used here 
> https://github.com/sum01/FindBerkeleyDB/blob/master/FindBerkeleyDB.cmake#L54

Great, thanks for the fix! I pushed it master!

> About `dbtextdb`. In the source tree present module `db_dbtext` and no module 
> `db_dbtextdb`. But in the `kamctl` utility present `dbtext` and `dbtextdb`. 
> https://github.com/kamailio/kamailio/tree/master/utils/kamctl/dbtextdb
> 
> Looks like `dbtext` installed properly. But `dbtextdb` is not.

Yeah, sorry I missed that part! Should also be installed now!


-- 
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4085#issuecomment-2582468397
You are receiving this because you are subscribed to this thread.

Message ID: <kamailio/kamailio/pull/4085/c2582468...@github.com>
_______________________________________________
Kamailio - Development Mailing List -- sr-dev@lists.kamailio.org
To unsubscribe send an email to sr-dev-le...@lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the 
sender!

Reply via email to