[asterisk-users] Asterisk 1.8.0-beta1 is Now Available!

Tzafrir Cohen tzafrir.cohen at xorcom.com
Sat Jul 24 18:20:51 CDT 2010


On Sat, Jul 24, 2010 at 12:01:25PM -0500, Tilghman Lesher wrote:
> On Saturday 24 July 2010 09:24:08 Russell Bryant wrote:
> > ----- Original Message -----
> >
> > > Well, looking at messages turned up these, maybe it will help?
> > >
> > > WARNING[28505] loader.c: Error loading module 'chan_dahdi.so':
> > > /usr/lib/asterisk/modules/chan_dahdi.so: undefined symbol:
> > > ast_smdi_interface_unref
> > > WARNING[28505] loader.c: Error loading module 'app_stack.so':
> > > /usr/lib/asterisk/modules/app_stack.so: undefined symbol:
> > > ast_agi_unregister
> > > WARNING[28505] loader.c: Error loading module 'func_aes.so':
> > > /usr/lib/asterisk/modules/func_aes.so: undefined symbol:
> > > ast_aes_set_decrypt_key
> > > WARNING[28505] loader.c: Error loading module 'app_voicemail.so':
> > > /usr/lib/asterisk/modules/app_voicemail.so: undefined symbol:
> > > ast_smdi_mwi_message_destroy
> >
> > Thank you for posting information about the problem that you hit.  These
> > look related to some changes in 1.8 that were made to make modules that
> > were previously hard requirements optional.  For example, chan_dahdi
> > required res_smdi, but now it's supposed to work regardless of whether or
> > not it is loaded.  With those changes in place, you are _never_ supposed to
> > get these errors.
> >
> > Please open an issue on http://issues.asterisk.org/ for this problem. 
> > Please include your config.log file, as well as what distro you are using,
> > and the version of gcc that you have (gcc --version).
> >
> > Thanks again for the feedback,
> 
> The version of gcc is most definitely related to this problem, although it is
> the linker that is the problem.  My recommendation for solving this problem
> is to use 'make menuselect' to eliminate any modules that you do not wish
> to load, then ensure modules that you definitely want (app_stack,
> app_voicemail) are selected.  Follow that up by eliminating all "noload"
> statements from /etc/asterisk/modules.conf and Asterisk should load fine.

But that would kill the test case :-)

Were the modules involved actually built? (sanity check: move
/usr/lib/asterisk/modules aside, and re-run 'make install')

-- 
               Tzafrir Cohen
icq#16849755              jabber:tzafrir.cohen at xorcom.com
+972-50-7952406           mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com  iax:guest at local.xorcom.com/tzafrir



More information about the asterisk-users mailing list