[asterisk-dev] [Code Review] 4151: Fix compiler error when using ./configure --enable-dev-mode --enable-coverage

wdoekes reviewboard at asterisk.org
Mon Nov 10 01:58:09 CST 2014


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/4151/#review13715
-----------------------------------------------------------

Ship it!


Ship It!

- wdoekes


On Nov. 8, 2014, 6:29 p.m., Corey Farrell wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviewboard.asterisk.org/r/4151/
> -----------------------------------------------------------
> 
> (Updated Nov. 8, 2014, 6:29 p.m.)
> 
> 
> Review request for Asterisk Developers.
> 
> 
> Bugs: ASTERISK-24502
>     https://issues.asterisk.org/jira/browse/ASTERISK-24502
> 
> 
> Repository: Asterisk
> 
> 
> Description
> -------
> 
> When coverage and dev-mode are enabled with DONT_OPTIMIZE, it causes build failure.  The double compilation does a 'shadow' build of each file with output to /dev/null.  Unfortunately when coverage is enabled, GCC tries writing to /dev/null.gcno (at least some versions do).  This prevents the build from proceeding.
> 
> This change prevents coverage from being enabled for the shadow build of all files.  This involves using a separate variable to hold the CFLAGS for coverage, and adding it to the commands for all real builds.
> 
> 
> Diffs
> -----
> 
>   /branches/11/Makefile.rules 427380 
> 
> Diff: https://reviewboard.asterisk.org/r/4151/diff/
> 
> 
> Testing
> -------
> 
> Build with these options now works in Linux Mint 17 (gcc 4.8.2-19ubuntu1).
> 
> 
> Thanks,
> 
> Corey Farrell
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20141110/287a8126/attachment.html>


More information about the asterisk-dev mailing list