[asterisk-bugs] [Asterisk 0016342]: [patch] configure fails to detect spandsp/expose.h when not in system include path

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16342 
====================================================================== 
Reported By:                bklang
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16342
Category:                   Core/BuildSystem
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-11-28 17:04 CST
Last Modified:              2010-01-14 17:27 CST
====================================================================== 
Summary:                    [patch] configure fails to detect spandsp/expose.h
when not in system include path
Description: 
configure has a flag to specify the path to spandsp, if it is not installed
into the system default path.  This works well for most of the spandsp
checks (such as spandsp.h), however it fails to properly detect the
spandsp/expose.h header.  This is partly due to the fact that the autoconf
check is different (AC_CHECK_HEADER vs. AST_EXT_LIB_CHECK) and so does not
inherit the proper CFLAGS.
====================================================================== 

---------------------------------------------------------------------- 
 (0116701) bklang (reporter) - 2010-01-14 17:27
 https://issues.asterisk.org/view.php?id=16342#c116701 
---------------------------------------------------------------------- 
seanbright: Yes, I did regenerate configure.  The behavior and error
messages also changed after the patch was applied and the new configure
ran. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-01-14 17:27 bklang         Note Added: 0116701                          
======================================================================