search

slomkowski / mumsi

SIP to Mumble gateway/bridge using PJSUA stack.
Apache License 2.0
41 stars 33 forks source link

Issue building with all sorts of workarounds #7

Closed tsolace closed 8 years ago

tsolace commented 8 years ago 
concerned@opinions:~/mumsi/build$ uname -a
Linux opinions 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u5 (2015-10-09) x86_64 GNU/Linux

My hacky workaround was, I cloned a repo for pjproject I found and took all the includes (it needed , then json.h in pjp util) that the build process for mumsi couldn't find from what I installed in the debian repos, put them in the mumlib include dir.

I have no idea what a working setup should be.

concerned@opinions:~/mumsi/build$ cmake ..
-- Boost version: 1.55.0
-- Found the following Boost libraries:
--   system
--   regex
-- Configuring done
-- Generating done
-- Build files have been written to: /home/concerned/mumsi/build
concerned@opinions:~/mumsi/build$ make
[ 14%] Building CXX object CMakeFiles/mumsi.dir/PjsuaCommunicator.cpp.o
In file included from /home/concerned/mumsi/../mumlib/include/pjsip.h:44:0,
                 from /home/concerned/mumsi/../mumlib/include/pjsua-lib/pjsua.h:30,
                 from /home/concerned/mumsi/PjsuaCommunicator.hpp:7,
                 from /home/concerned/mumsi/PjsuaCommunicator.cpp:1:
/home/concerned/mumsi/../mumlib/include/pjsip/sip_transport_tcp.h:113:5: error: ‘pj_sockopt_params’ does not name a type
     pj_sockopt_params sockopt_params;
     ^
In file included from /home/concerned/mumsi/../mumlib/include/pjsip.h:45:0,
                 from /home/concerned/mumsi/../mumlib/include/pjsua-lib/pjsua.h:30,
                 from /home/concerned/mumsi/PjsuaCommunicator.hpp:7,
                 from /home/concerned/mumsi/PjsuaCommunicator.cpp:1:
/home/concerned/mumsi/../mumlib/include/pjsip/sip_transport_tls.h:233:5: error: ‘pj_sockopt_params’ does not name a type
     pj_sockopt_params sockopt_params;
     ^
/home/concerned/mumsi/../mumlib/include/pjsip/sip_transport_tls.h: In function ‘void pjsip_tls_setting_default(pjsip_tls_setting*)’:
/home/concerned/mumsi/../mumlib/include/pjsip/sip_transport_tls.h:73:10: error: ‘PJ_SSL_SOCK_PROTO_TLS1_1’ was not declared in this scope
          PJ_SSL_SOCK_PROTO_TLS1_1 | \
          ^
/home/concerned/mumsi/../mumlib/include/pjsip/sip_transport_tls.h:274:22: note: in expansion of macro ‘PJSIP_SSL_DEFAULT_PROTO’
     tls_opt->proto = PJSIP_SSL_DEFAULT_PROTO;
                      ^
/home/concerned/mumsi/../mumlib/include/pjsip/sip_transport_tls.h:74:10: error: ‘PJ_SSL_SOCK_PROTO_TLS1_2’ was not declared in this scope
          PJ_SSL_SOCK_PROTO_TLS1_2)
          ^
/home/concerned/mumsi/../mumlib/include/pjsip/sip_transport_tls.h:274:22: note: in expansion of macro ‘PJSIP_SSL_DEFAULT_PROTO’
     tls_opt->proto = PJSIP_SSL_DEFAULT_PROTO;
                      ^
In file included from /home/concerned/mumsi/PjsuaCommunicator.hpp:7:0,
                 from /home/concerned/mumsi/PjsuaCommunicator.cpp:1:
/home/concerned/mumsi/../mumlib/include/pjsua-lib/pjsua.h: At global scope:
/home/concerned/mumsi/../mumlib/include/pjsua-lib/pjsua.h:2310:5: error: ‘pj_sockopt_params’ does not name a type
     pj_sockopt_params sockopt_params;
     ^
/home/concerned/mumsi/../mumlib/include/pjsua-lib/pjsua.h:6184:44: error: ‘pjmedia_wav_player_info’ has not been declared
                                            pjmedia_wav_player_info *info);
                                            ^
CMakeFiles/mumsi.dir/build.make:54: recipe for target 'CMakeFiles/mumsi.dir/PjsuaCommunicator.cpp.o' failed
make[2]: *** [CMakeFiles/mumsi.dir/PjsuaCommunicator.cpp.o] Error 1
CMakeFiles/Makefile2:60: recipe for target 'CMakeFiles/mumsi.dir/all' failed
make[1]: *** [CMakeFiles/mumsi.dir/all] Error 2
Makefile:76: recipe for target 'all' failed
make: *** [all] Error 2
concerned@opinions:~/mumsi/build$
slomkowski commented 8 years ago

What version of PJSIP library are you using? Is it 2.1.0.0 as in current jessie? In Debian I see a lot of packages matching libpj. I'm not sure if all of them are required. I myself use current PJSIP compiled from source since I had problems at runtime.

tsolace commented 8 years ago

@slomkowski I'm using pjproject (2.1.0.0.ast20130823-1) unstable; urgency=low

tsolace commented 8 years ago

Compiling/installing pjproject from the tarball on the official website gets mumsi to compile flawlessly. I should have tried that first, heh.

slomkowski commented 8 years ago

I don't know what the problem is, I've tested mumsi under Debian 8 with standard packages some time ago and it compiled successfully. For good measure make sure packages libpjsua2 libpjproject-dev libpjsip-ua2 libpj2 libpjsip2 are installed.