<p dir="ltr">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? <br>
</p>
<div class="gmail_quote">On Sep 19, 2013 12:24 PM, "Vlad Paiu" <<a href="mailto:vladpaiu@opensips.org">vladpaiu@opensips.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Hello,<br>
<br>
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 ?<br>
<br>
Best Regards,<br>
<pre cols="72">Vlad Paiu
OpenSIPS Developer
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a>
</pre>
On 16.09.2013 15:28, Jared Evans wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Here's the pastebin of the steps I took to compile
opensips 1.10.0 after using menuconfig to select modules to be
included.
<div><br>
</div>
<div><a href="http://pastebin.com/HBsg8S1M" target="_blank">http://pastebin.com/HBsg8S1M</a><br>
</div>
<div><br>
</div>
<div>There are two errors:</div>
<div><br>
</div>
<div><span>lock_alloc.h:60:2:
error: #error "locking requires shared memory support" </span></div>
<div><span>I'm
assuming that this error shouldn't have took place if I
compiled with </span><span>CFLAGS="-DSHM_MEM
-DUSE_SHM_MEM"</span><span> which
builds in shared memory support.</span></div>
<div><br>
</div>
<div>This is may be related to another error down the road:</div>
<div><font color="#000000" face="Consolas, Menlo, Monaco, Lucida
Console, Liberation Mono, DejaVu Sans Mono, Bitstream Vera
Sans Mono, monospace, serif"><span style="font-size:12px;line-height:21px">ut.c:(.text+0x220):
undefined reference to `pkg_realloc'</span></font><br>
</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Mon, Sep 16, 2013 at 3:08 AM, Vlad
Paiu <span dir="ltr"><<a href="mailto:vladpaiu@opensips.org" target="_blank">vladpaiu@opensips.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Hello,<br>
<br>
What were the errors encountered when trying to run
menuconfig on Ubuntu 13.04 ?<br>
<br>
Best Regards,<br>
Vlad<br>
<pre cols="72">Vlad Paiu
OpenSIPS Developer
<a href="http://www.opensips-solutions.com" target="_blank">http://www.opensips-solutions.com</a>
</pre>
<div>
<div> On 16.09.2013 06:19, Jared Evans
wrote:<br>
</div>
</div>
</div>
<blockquote type="cite">
<div>
<div>
<div dir="ltr">
<div>Hi all,</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
<div>Here are the steps I took on Ubuntu 13.04:</div>
<div><br>
</div>
<div>After untar opensips1.10, instead of running
menuconfig, manually edit Makefile.conf to
exclude/include desired modules.</div>
<div><br>
</div>
<div>make all CFLAGS="-fPIC -DSHM_MEM
-DUSE_SHM_MEM -DUSE_TCP" TLS="1"</div>
<div>-fPIC so that modules can be compiled </div>
<div>-DSHM_MEM -DUSE_SHM_MEM because some modules
requires shared memory<br>
</div>
<div>-DUSE_TCP include TCP in the build<br>
</div>
<div>TLS=1 include experimental TLS in the build</div>
<div><br>
</div>
<div>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.</div>
<div><br>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div>
</div>
<pre>_______________________________________________
Users mailing list
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</div>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Users mailing list
<a href="mailto:Users@lists.opensips.org" target="_blank">Users@lists.opensips.org</a>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a>
</pre>
</blockquote>
<br>
</div>
<br>_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@lists.opensips.org">Users@lists.opensips.org</a><br>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users" target="_blank">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><br>
<br></blockquote></div>