Hello,
I've just tried to replicate this and can't seem to do it by using
menuconfig to select modules to be enabled. Can you perhaps open a bug
report on github about this and let me know the exact steps you go
through that leads to this bug ?
If you want to check if shared memory is disabled, open Makefile.conf
and check if the DEFS+= -DSHM_MEM line is commented or not.
Best Regards,
Vlad Paiu
OpenSIPS Developer
http://www.opensips-solutions.com
On 19.09.2013 23:05, Jared Evans wrote:
Yes, it's reliably reproduced when using menuconfig to select modules
to be enabled. Where can I check to see if shared memory option is
disabled for the compilation?
On Sep 19, 2013 12:24 PM, "Vlad Paiu" <vladp...@opensips.org
<mailto:vladp...@opensips.org>> wrote:
Hello,
It seems that somehow, you've disabled shared memory support - and
that's way you see those compilation errors - seems like a bug in
the menuconfig tool. Can you replicate this menuconfig behavior ?
Best Regards,
Vlad Paiu
OpenSIPS Developer
http://www.opensips-solutions.com
On 16.09.2013 15:28, Jared Evans wrote:
Here's the pastebin of the steps I took to compile opensips
1.10.0 after using menuconfig to select modules to be included.
http://pastebin.com/HBsg8S1M
There are two errors:
lock_alloc.h:60:2: error: #error "locking requires shared memory
support"
I'm assuming that this error shouldn't have took place if I
compiled with CFLAGS="-DSHM_MEM -DUSE_SHM_MEM" which builds in
shared memory support.
This is may be related to another error down the road:
ut.c:(.text+0x220): undefined reference to `pkg_realloc'
On Mon, Sep 16, 2013 at 3:08 AM, Vlad Paiu <vladp...@opensips.org
<mailto:vladp...@opensips.org>> wrote:
Hello,
What were the errors encountered when trying to run
menuconfig on Ubuntu 13.04 ?
Best Regards,
Vlad
Vlad Paiu
OpenSIPS Developer
http://www.opensips-solutions.com
On 16.09.2013 06:19, Jared Evans wrote:
Hi all,
It seems like using console GUI menuconfig to
include/exclude modules causes problems later when trying to
compile on an Ubuntu system. I worked around this by
skipping the menuconfig step and manually edit Makefile.conf
to include/exclude modules.
Here are the steps I took on Ubuntu 13.04:
After untar opensips1.10, instead of running menuconfig,
manually edit Makefile.conf to exclude/include desired modules.
make all CFLAGS="-fPIC -DSHM_MEM -DUSE_SHM_MEM -DUSE_TCP"
TLS="1"
-fPIC so that modules can be compiled
-DSHM_MEM -DUSE_SHM_MEM because some modules requires shared
memory
-DUSE_TCP include TCP in the build
TLS=1 include experimental TLS in the build
if you see any compilation failures at this point, it's
likely due to missing library that needs to be installed but
the error message will give you a clear hint about which
library is missing. Once all the libraries required by the
included modules are installed, you should have a successful
compilation then opensips can be installed on your system.
_______________________________________________
Users mailing list
Users@lists.opensips.org <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org <mailto:Users@lists.opensips.org>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users