[asterisk-bugs] [Asterisk 0012289]: [patch] Cannot compile asterisk with DONT_OPTIMIZE on a 2.4 kernel and an old version of Slackware

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=12289 
====================================================================== 
Reported By:                francesco_r
Assigned To:                Corydon76
====================================================================== 
Project:                    Asterisk
Issue ID:                   12289
Category:                   Utilities/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     feedback
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  1.4  
SVN Revision (number only!): 110395 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             03-24-2008 11:11 CDT
Last Modified:              05-12-2008 11:26 CDT
====================================================================== 
Summary:                    [patch] Cannot compile asterisk with DONT_OPTIMIZE
on a 2.4 kernel and an old version of Slackware
Description: 
I use Slackware 11 (gcc 3.4.6)

   [CC] chan_phone.c -> chan_phone.o
In file included from /usr/src/asterisk-1.4/include/asterisk/cdr.h:49,
                 from
/usr/src/asterisk-1.4/include/asterisk/channel.h:115,
                 from chan_phone.c:57:
/usr/src/asterisk-1.4/include/asterisk/utils.h: In function
`_ast_asprintf':
/usr/src/asterisk-1.4/include/asterisk/utils.h:476: sorry, unimplemented:
functi               on '_ast_asprintf' can never be inlined because it
uses variable argument lists
make[1]: *** [chan_phone.o] Error 1

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

---------------------------------------------------------------------- 
 davidw - 05-12-08 11:26  
---------------------------------------------------------------------- 
I didn't actually try defining LOW_MEMORY, but the way I read the code,
doing so would be a workaround, if you completely reverted the patch.

What LOW_MEMORY does is to inhibit inlining, but the macro still needs to
generate the actual body in only one place.  What my extra macro did was to
allow one to effectively force the LOW_MEMORY behaviour in just the problem
case, so that one didn't inhibit inlining elsewhere. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
05-12-08 11:26  davidw         Note Added: 0086721                          
======================================================================