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.
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
c
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 too
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
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" wrote:
> Hello,
>
> It seems that somehow, you've disabled shared memory support - and th
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 disabl
