<HTML>
<HEAD>
<TITLE>Re: [OpenSIPS-Users] Opensip-cp and xml-rpc-c question</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Nevermind, I was able to get this to work...with help from a co-worker. Works on CentOS 5.4 64bit<BR>
<BR>
Instead of downloading the latest .tar file, we used SVN and got the latest xmlrpc-c source. <BR>
<BR>
Then,<BR>
<B>./configure --disable-abyss-threads<BR>
make<BR>
make install<BR>
</B><BR>
And then recompiled opensips<BR>
<BR>
On 4/28/10 9:45 AM, "Sven Schulz" <<a href="svens@psu.edu">svens@psu.edu</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Alex, I just tried what you said and it still doesn’t work. Are there any dependencies for xml-rpc-c that I need? Also, Im using 64 bit, if that matters.<BR>
<BR>
Sven<BR>
<BR>
<BR>
On 4/28/10 4:49 AM, "Alex Ionescu" <<a href="alex@opensips.org">alex@opensips.org</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Hi Sven,<BR>
<BR>
For your first question : <BR>
"Can I use mi_datagram instead of mi_xmlrpc for opensips-cp? "<BR>
Well, it is not suported ... yet. So, unfortunately, you cannot use mi_datagram.<BR>
<BR>
For the second question :<BR>
"If not, how to I compile xml-rpc-c into Centos5?"<BR>
We've recently installed CP and OpenSIPS on a Centos 5 server. We've used <B>xmlrpc-c-1.06.38</B> <BR>
To install it please do : <B>./configure --disable-abyss-threads</B> (this is very important) ... then you do as usual <B>make all</B> and <B>make install</B>.<BR>
<BR>
I hope you will succeed eventually !<BR>
<BR>
Regards,<BR>
Alex<BR>
<BR>
<BR>
<BR>
On 4/27/2010 22:58, Sven Schulz wrote: <BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'> Opensip-cp and xml-rpc-c question 2 part Question:<BR>
<BR>
<BR>
</SPAN></FONT><OL><LI><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>Can I use mi_datagram instead of mi_xmlrpc for opensips-cp?
</SPAN></FONT><LI><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>If not, how to I compile xml-rpc-c into Centos5?
</SPAN></FONT><LI><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'> <BR>
</SPAN></FONT></OL><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'> <BR>
I cant compile the recommended version (.09.10) into 64bit. <BR>
If I download the latest SRC, I get these errors at the end of MAKE:<BR>
<BR>
/usr/bin/ld: XmlRpcCpp.o: relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC<BR>
XmlRpcCpp.o: could not read symbols: Bad value<BR>
collect2: ld returned 1 exit status<BR>
make[2]: *** [libxmlrpc_cpp.so.3.06] Error 1<BR>
make[2]: Leaving directory `/usr/src/xmlrpc-c-1.06.38/src/cpp'<BR>
make[1]: *** [cpp/all] Error 2<BR>
make[1]: Leaving directory `/usr/src/xmlrpc-c-1.06.38/src'<BR>
make: *** [src/all] Error 2<BR>
<BR>
<BR>
Any help would be appreciated. <BR>
<BR>
<BR>
_______________________________________________<BR>
Users mailing list<BR>
<a href="Users@lists.opensips.org">Users@lists.opensips.org</a><BR>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
</SPAN></FONT></BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'><BR>
<HR ALIGN=CENTER SIZE="3" WIDTH="95%"></SPAN></FONT><FONT SIZE="2"><FONT FACE="Consolas, Courier New, Courier"><SPAN STYLE='font-size:10pt'>_______________________________________________<BR>
Users mailing list<BR>
<a href="Users@lists.opensips.org">Users@lists.opensips.org</a><BR>
<a href="http://lists.opensips.org/cgi-bin/mailman/listinfo/users">http://lists.opensips.org/cgi-bin/mailman/listinfo/users</a><BR>
</SPAN></FONT></FONT></BLOCKQUOTE>
</BODY>
</HTML>