For example, If I modify only the registrar module, I thought the steps were:
1. make modules=modules\registrar modules 2. copy the registrar.so to the installed path
And when starting kamailio I got the error message below:
ERROR: <core> [sr_module.c:417]: version_control(): ERROR: module compile flags mismatch for [my installed path]/registrar.so
I've searched for the answer and it seems to need to re-build and re-install kamailio and all the module again...
Is there more efficient way for just updating the specified module ??
Thanks a lot.:)
I found it's work if I make under the specified module directory... but still can not figure out why it gets error if under the main directory.
2015-03-04 11:48 GMT+08:00 jack wang antirazin@gmail.com:
For example, If I modify only the registrar module, I thought the steps were:
- make modules=modules\registrar modules
- copy the registrar.so to the installed path
And when starting kamailio I got the error message below:
ERROR: <core> [sr_module.c:417]: version_control(): ERROR: module compile flags mismatch for [my installed path]/registrar.so
I've searched for the answer and it seems to need to re-build and re-install kamailio and all the module again...
Is there more efficient way for just updating the specified module ??
Thanks a lot.:)
Subject: [SR-Users] Any suggestion if I just want to update one or some modules? Date: Wed, Mar 04, 2015 at 11:48:46AM +0800 Quoting jack wang (antirazin@gmail.com):
Is there more efficient way for just updating the specified module ??
FWIW, I did exactly that, on FreeBSD:
cd srcpath/modules/module rm *.o gmake gmake install
Removing the object code is a "gmake clean light" that is enough to trigger enough rebuilding. Some operations are performed in the "gmake install" step, so just copying the relinked object after "gmake" won't do. Or sometimes, it might, but that seems to be dependent on which module you are building.
I've been lucky with RADIUS, xml and postgres modules. Also, what triggered my rebuilds was library upgrades, ie. going from postgres 9.1 to 9.3 and resulting relinking needs.
We did also do a bit of printf debugging code changes in some modules, and that also worked.
-
jack wang -
Måns Nilsson