[asterisk-bugs] [Asterisk 0014846]: [patch] undefined symbols - modules can't be loaded

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14846 
====================================================================== 
Reported By:                pj
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   14846
Category:                   Core/BuildSystem
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1 
SVN Revision (number only!): 186622 
Request Review:              
====================================================================== 
Date Submitted:             2009-04-07 10:49 CDT
Last Modified:              2009-04-13 11:58 CDT
====================================================================== 
Summary:                    [patch] undefined symbols - modules can't be loaded
Description: 
After updating from 
Asterisk SVN-branch-1.6.1-r175257
to
Asterisk SVN-branch-1.6.1-r186622
some modules can't be loaded
compiled with 
--->  Compiler Flags
[*] DONT_OPTIMIZE
[*] DEBUG_THREADS
[*] LOADABLE_MODULES
[*] DEBUG_CHANNEL_LOCKS
[*] MALLOC_DEBUG


====================================================================== 

---------------------------------------------------------------------- 
 (0103152) plack (reporter) - 2009-04-13 11:58
 http://bugs.digium.com/view.php?id=14846#c103152 
---------------------------------------------------------------------- 
pj: the patch I submitted just reverts previous behavior.  If there are not
SMDI interfaces, the module would alway produce an error, but would not
unload.

tilghman is correct that the best way to permanently fix this issue (that
was attempted by the original change) is to make it optional.

It does appear that 1.6.2 and trunk both have his changes.

The question becomes if you can live with the old behavior (prior to
r188019) or not. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-04-13 11:58 plack          Note Added: 0103152                          
======================================================================