cap_set_proc on several modules after installation from source

Home » Asterisk Users » cap_set_proc on several modules after installation from source
Asterisk Users 3 Comments

Hello Folks,

What could be producing the following warnings on console, after an
installation from source (Asterisk 1.4.41):

[May 12 21:36:54] WARNING[15344]: loader.c:434 load_dynamic_module:
Error loading module ‘res_musiconhold.so’:
/usr/lib/asterisk/modules/res_musiconhold.so: undefined symbol:
cap_set_proc

[May 12 21:36:54] WARNING[15344]: loader.c:434 load_dynamic_module:
Error loading module ‘app_festival.so’:
/usr/lib/asterisk/modules/app_festival.so: undefined symbol:
cap_set_proc

[May 12 21:36:55] WARNING[15344]: loader.c:434 load_dynamic_module:
Error loading module ‘app_ices.so’:
/usr/lib/asterisk/modules/app_ices.so: undefined symbol: cap_set_proc
[May 12 21:36:55] WARNING[15344]: loader.c:434 load_dynamic_module:
Error loading module ‘app_mp3.so’: /usr/lib/asterisk/modules/app_mp3.so:
undefined symbol: cap_set_proc
[May 12 21:36:55] WARNING[15344]: loader.c:434 load_dynamic_module:
Error loading module ‘app_nbscat.so’:
/usr/lib/asterisk/modules/app_nbscat.so: undefined symbol: cap_set_proc
[May 12 21:36:55] WARNING[15344]: loader.c:434 load_dynamic_module:
Error loading module ‘app_externalivr.so’:
/usr/lib/asterisk/modules/app_externalivr.so: undefined symbol:
cap_set_proc

[May 12 21:36:55] WARNING[15344]: loader.c:434 load_dynamic_module:
Error loading module ‘app_dahdiras.so’:
/usr/lib/asterisk/modules/app_dahdiras.so: undefined symbol: cap_set_proc

Uname -a:
Linux eslackware 2.6.33.4-smp #2 SMP Wed May 12 22:47:36 CDT 2010 i686
Intel(R) Core(TM)2 Duo CPU E4500 @ 2.20GHz GenuineIntel GNU/Linux

gcc -v:
Reading specs from /usr/lib/gcc/i486-slackware-linux/4.4.4/specs
Target: i486-slackware-linux
Configured with: ../gcc-4.4.4/configure –prefix=/usr –libdir=/usr/lib

3 thoughts on - cap_set_proc on several modules after installation from source

  • Tzafrir Cohen wrote:

    Could this be related to having used ‘strip’ on the binaries?

    Note: I have previously compiled/installed Asterisk 1.4.X on a fresh
    install of Slackware 13.X and never faced this before.