Hi all,
I hope this is the right group for my question. It's related to a Kamailio build. I tried to build Kamailio in RHEL7 and I encountered some problems I could fix it locally. I tried to find any email in the user and the developer Kamailio groups by skimming the mails, however there is no clue about it. I need to know your opinion about it.
The build error is:
*******************************************************************
CC (gcc) [M app_sqlang.so] app_sqlang_api.o
CC (gcc) [M app_sqlang.so] app_sqlang_kemi_export.o
CC (gcc) [M app_sqlang.so] app_sqlang_mod.o
make --no-print-directory -C ./squirrel/squirrel SQMARCH64="-m64" CC_EXTRA_FLAGS="-fPIC" \
OUT="../../libsquirrel.a" sq64
gcc -O2 -m64 -D_SQ64 -fno-exceptions -fno-rtti -Wall -fno-strict-aliasing -c sqapi.cpp sqbaselib.cpp sqfuncstate.cpp sqdebug.cpp sqlexer.cpp sqobject.cpp sqcompiler.cpp sqstate.cpp sqtable.cpp sqmem.cpp sqvm.cpp sqclass.cpp -I../include -I. -Iinclude -fPIC
In file included from sqpcheader.h:14:0,
from sqapi.cpp:4:
/usr/include/c++/4.8.2/new:39:28: fatal error: bits/c++config.h: No such file or directory
#include <bits/c++config.h>
^
compilation terminated.
...
******************************************************************
As you can see above, the make command stopped in app_sqlang.so stage due to an including error. These problems are classic for builds on RHEL7 for a lot of tools we need to compile. So, I'm familiar with it and fixed it easily:
I just appended "-I/usr/include/c++/4.8.2/i686-redhat-linux/" in "INCZ?= -I$(SQUIRREL)/include -I." row for both ./src/modules/app_sqlang/squirrel/sqstdlib/Makefile and ./src/modules/app_sqlang/squirrel/squirrel/Makefile
Then Kamailio build is finished properly.
Uname output is here:
Linux gearbox07 3.10.0-862.6.3.el7.x86_64 #1 SMP Fri Jun 15 17:57:37 EDT 2018 x86_64 x86_64 x86_64 GNU/Linux
My question is that if it's normal or not. Is there anybody who built Kamailio on RHEL7 environment here? Would you help me to understand the situation, please?
Thanks...
S. Cumhur Karahan
[http://s.turkcell.com.tr/SiteAssets/Genel/mail-imza.jpg] <https://tvplus.com.tr/>
Bu elektronik posta ve onunla iletilen butun dosyalar sadece gondericisi tarafindan almasi amaclanan yetkili gercek ya da tuzel kisinin kullanimi icindir. Eger soz konusu yetkili alici degilseniz bu elektronik postanin icerigini aciklamaniz, kopyalamaniz, yonlendirmeniz ve kullanmaniz kesinlikle yasaktir ve bu elektronik postayi derhal silmeniz gerekmektedir.
TURKCELL bu mesajin icerdigi bilgilerin do?rulu?u veya eksiksiz oldugu konusunda herhangi bir garanti vermemektedir. Bu nedenle bu bilgilerin ne sekilde olursa olsun iceriginden, iletilmesinden, alinmasindan ve saklanmasindan sorumlu degildir. Bu mesajdaki gorusler yalnizca gonderen kisiye aittir ve TURKCELLin goruslerini yansitmayabilir
Bu e-posta bilinen butun bilgisayar viruslerine karsi taranmistir.
________________________________
This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient you are hereby notified that any dissemination, forwarding, copying or use of any of the information is strictly prohibited, and the e-mail should immediately be deleted.
TURKCELL makes no warranty as to the accuracy or completeness of any information contained in this message and hereby excludes any liability of any kind for the information contained therein or for the information transmission, reception, storage or use of such in any way whatsoever. The opinions expressed in this message belong to sender alone and may not necessarily reflect the opinions of TURKCELL.
This e-mail has been scanned for all known computer viruses.
#### Pre-Submission Checklist
- [x] Commit message has the format required by CONTRIBUTING guide
- [x] Commits are split per component (core, individual modules, libs, utils, ...)
- [x] Each component has a single commit (if not, squash them into one commit)
- [x] No commits to README files for modules (changes must be done to docbook files
in `doc/` subfolder, the README file is autogenerated)
#### Type Of Change
- [x] Small bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds new functionality)
- [ ] Breaking change (fix or feature that would change existing functionality)
#### Checklist:
- [ ] PR should be backported to stable branches
- [x] Tested changes locally
- [ ] Related to issue #XXXX (replace XXXX with an open issue number)
#### Description
This is to align behavior with the remaining checks. The example configuration enable the content length sanity check and prior to this change would warn when SIP messages without body were received.
You can view, comment on, or merge this pull request online at:
https://github.com/kamailio/kamailio/pull/2211
-- Commit Summary --
* sanity: use debug log level when content length header is missing
-- File Changes --
M src/modules/sanity/sanity.c (2)
-- Patch Links --
https://github.com/kamailio/kamailio/pull/2211.patchhttps://github.com/kamailio/kamailio/pull/2211.diff
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/2211
Module: kamailio
Branch: 5.3
Commit: b98bdc21dc495ca2f4babcc6a556b9c0dc63884a
URL: https://github.com/kamailio/kamailio/commit/b98bdc21dc495ca2f4babcc6a556b9c…
Author: Henning Westerholt <hw(a)skalatan.de>
Committer: Henning Westerholt <hw(a)skalatan.de>
Date: 2020-02-03T11:57:37+01:00
tm: use WARN log level for status rewrite by UAS (were decreased before SER tm integration)
- use WARN log level for status rewrite by UAS (log level decreased before SER
tm integration, e.g. v1.5.x)
- for bad interconnection or gateways this might be reported frequently
(cherry picked from commit e1a01699af450292859e4f2cd69b6a6d85246e5e)
---
Modified: src/modules/tm/t_reply.c
---
Diff: https://github.com/kamailio/kamailio/commit/b98bdc21dc495ca2f4babcc6a556b9c…
Patch: https://github.com/kamailio/kamailio/commit/b98bdc21dc495ca2f4babcc6a556b9c…
---
diff --git a/src/modules/tm/t_reply.c b/src/modules/tm/t_reply.c
index 331bdbdf71..77747d34c0 100644
--- a/src/modules/tm/t_reply.c
+++ b/src/modules/tm/t_reply.c
@@ -1307,7 +1307,7 @@ static enum rps t_should_relay_response( struct cell *Trans , int new_code,
}
/* this looks however how a very strange status rewrite attempt;
* report on it */
- LM_ERR("status rewrite by UAS: stored: %d, received: %d\n",
+ LM_WARN("status rewrite by UAS: stored: %d, received: %d\n",
Trans->uac[branch].last_received, new_code);
goto discard;
}
Module: kamailio
Branch: 5.2
Commit: b370041ccfd86e15812e1a06ad803569654eac07
URL: https://github.com/kamailio/kamailio/commit/b370041ccfd86e15812e1a06ad80356…
Author: Henning Westerholt <hw(a)skalatan.de>
Committer: Henning Westerholt <hw(a)skalatan.de>
Date: 2020-02-03T11:57:07+01:00
tm: use WARN log level for status rewrite by UAS (were decreased before SER tm integration)
- use WARN log level for status rewrite by UAS (log level decreased before SER
tm integration, e.g. v1.5.x)
- for bad interconnection or gateways this might be reported frequently
(cherry picked from commit e1a01699af450292859e4f2cd69b6a6d85246e5e)
---
Modified: src/modules/tm/t_reply.c
---
Diff: https://github.com/kamailio/kamailio/commit/b370041ccfd86e15812e1a06ad80356…
Patch: https://github.com/kamailio/kamailio/commit/b370041ccfd86e15812e1a06ad80356…
---
diff --git a/src/modules/tm/t_reply.c b/src/modules/tm/t_reply.c
index d4ed5592ec..5840afd16f 100644
--- a/src/modules/tm/t_reply.c
+++ b/src/modules/tm/t_reply.c
@@ -1299,7 +1299,7 @@ static enum rps t_should_relay_response( struct cell *Trans , int new_code,
}
/* this looks however how a very strange status rewrite attempt;
* report on it */
- LM_ERR("status rewrite by UAS: stored: %d, received: %d\n",
+ LM_WARN("status rewrite by UAS: stored: %d, received: %d\n",
Trans->uac[branch].last_received, new_code);
goto discard;
}
Module: kamailio
Branch: master
Commit: e1a01699af450292859e4f2cd69b6a6d85246e5e
URL: https://github.com/kamailio/kamailio/commit/e1a01699af450292859e4f2cd69b6a6…
Author: Henning Westerholt <hw(a)skalatan.de>
Committer: Henning Westerholt <hw(a)skalatan.de>
Date: 2020-02-03T11:53:55+01:00
tm: use WARN log level for status rewrite by UAS (were decreased before SER tm integration)
- use WARN log level for status rewrite by UAS (log level decreased before SER
tm integration, e.g. v1.5.x)
- for bad interconnection or gateways this might be reported frequently
---
Modified: src/modules/tm/t_reply.c
---
Diff: https://github.com/kamailio/kamailio/commit/e1a01699af450292859e4f2cd69b6a6…
Patch: https://github.com/kamailio/kamailio/commit/e1a01699af450292859e4f2cd69b6a6…
---
diff --git a/src/modules/tm/t_reply.c b/src/modules/tm/t_reply.c
index 331bdbdf71..77747d34c0 100644
--- a/src/modules/tm/t_reply.c
+++ b/src/modules/tm/t_reply.c
@@ -1307,7 +1307,7 @@ static enum rps t_should_relay_response( struct cell *Trans , int new_code,
}
/* this looks however how a very strange status rewrite attempt;
* report on it */
- LM_ERR("status rewrite by UAS: stored: %d, received: %d\n",
+ LM_WARN("status rewrite by UAS: stored: %d, received: %d\n",
Trans->uac[branch].last_received, new_code);
goto discard;
}