| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index | Next in Thread > |
--- 11年9月27日，周二, Francis Joanis <francis.joanis@xxxxxxxxx> 写道：
日期: 2011年9月27日,周二,下午7:38
发件人: Francis Joanis <francis.joanis@xxxxxxxxx>
主题: Re: [reSIProcate-users] reSIProcate compilation errors on Fedora 15 & network down notification issue
收件人: "he yaxin" <crazyplayer1983@xxxxxxxxxxxx>
抄送: resiprocate-users@xxxxxxxxxxxxxxx
On Tue, Sep 27, 2011 at 7:43 AM, he yaxin <crazyplayer1983@xxxxxxxxxxxx> wrote:
--- 11年9月20日，周二, Francis Joanis <francis.joanis@xxxxxxxxx> 写道：
发件人: Francis Joanis <francis.joanis@xxxxxxxxx>
主题: Re: [reSIProcate-users] reSIProcate compilation errors on Fedora 15 & network down notification issue
收件人: "he yaxin" <crazyplayer1983@xxxxxxxxxxxx>
抄送: resiprocate-users@xxxxxxxxxxxxxxx
日期: 2011年9月20日,周二,下午5:36I’m trying to get reSIProcate built on Fedaro 15. I believe I have done everything said in the “Quick Subversion Checkout and Compilation HOWTO” for the compilation, but I am still getting errors:
Some of the errors are as follows:
Line 28 of ParserContainer.hxx:
typedef ptrdiff_t difference_type;
The compiler is saying “ptrdiff_t” is not definedLine 4282 of dumTests.cxx
if(signal(SIGPIPE, SIG_IGN)==SIG_ERR)
The compiler is saying “signal”, “SIGPIPE”, “SIG_IGN” and “SIG_ERR” were not declared in the scopeLine 93 of DtlsSocket.hxx and Line 48 of FlowDtlsSocketContext.cxx
SRTP_PROTECTION_PROFILE* getSrtpProfile();
SRTP_PROTECTION_PROTFILE *srtp_profile;
The compiler is saying “SRTP_PROTECTION_PROFILE” is not defined..........
According to the tutorial, everything should be compiled OK, but, apparently I got errors…I’m new to the Linux OS and I may not have done the configuration right on the makefile. Any veterans or people who have successfully resolved such issues could shed some light on this? Thanks very much sincerely.
The other issue is that has there been any implementation done in terms of network down notification or the reSIProcate Stack down notification in reSIProcate? There was a previous post saying that network down notification is not implemented because the actual code would be OS specific, but that post was 6 years ago.
Alex
_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/
Hi,
Are you trying to compile the mainline or a branch? To compile the main on Fedora 15 you need to apply this patch:
Index: resip/stack/ParserContainer.hxx
===================================================================
--- resip/stack/ParserContainer.hxx (revision 9267)
+++ resip/stack/ParserContainer.hxx (working copy)
@@ -10,6 +10,8 @@
namespace resip
{
+ using std::ptrdiff_t;
+
/**
@ingroup resip_crit
@brief Container class for ParserCategory, used by SipMessage.
I'll see about having this patch checked in the repository.
I do not know about the other errors... I'll look into them when I get a chance. Same for network down detection: I am not aware of anything currently implementing this in the code base.
Hope this helps,
Francis
===============================================================Thanks, Francis, the patch makes the build go further and I got the following errors while building sipXtapi for recon on Fedora 15.For sipXportLib
os/OsSSLServerSocket.cpp: In member function 'virtual OsConnectionSocket* OsSSLServerSocket::accept()':
os/OsSSLServerSocket.cpp:96:38: error: cannot pass objects of non-trivially-copyable type 'OsAtomicLightInt' through '...For sipXmediaLib:
gcc: error: codec_pcmapcmu.so: No such file or directory
gcc: error: unrecognized option '-soname'For sipXmediaAdapterLib:
depends on sipXmediaLib.la, thus failed to build
Has anybody encountered these error?And it seems to me that original make file builds everything of the reSIProcate code. I am wondering if there is a way I can only build and use the reSIProcate core SIP Stack and the DUM? Perhaps I should get to know how the code files are structured in the file system? Any suggestions?Thanks a lot!
Regards,
Alex
Hi,
I haven't played with the sipX* code for a long time, so I'm afraid I don't know why sipXportLib isn't compiling. If you really need to compile it you could ask on the sipX* mailing lists (http://list.sipfoundry.org/mailman/listinfo).
Do you really need to compile reCon? When you run ./configure, it should ask you what you want to compile. I mostly use resip + dum myself, so I answer "no" when asked whether I want to build Repro, reCon and reTurn.
Hope this helps,
Francis
===============================================================Thanks a lot, Francis. Actually, I will only use resip and dum. I am wondering if I can only build resip and dum solely and integrate them into my own application. I’ve looked at the reSIProcate make file and it is huge and I’m not sure where to start. What do you think is the best way to just integrate resip and dum into my own application and build them?
I also ran ./configure and disabled the build of reCon and reTurn and I am continuing to get new errors:
dumTests.cxx: In function ‘int main(int, char**)’:
dumTests.cxx:4282:17: error: ‘SIGPIPE’ was not declared in this scope
dumTests.cxx:4282:26: error: ‘SIG_IGN’ was not declared in this scope
dumTests.cxx:4282:33: error: ‘signal’ was not declared in this scope
dumTests.cxx:4282:38: error: ‘SIG_ERR’ was not declared in this scope
Everybody else’s comments are also welcomed! Thanks!
Regards,
Alex