[asterisk-bugs] [JIRA] (ASTERISK-27563) Build process ignores DONT_OPTIMIZE and always sets -O3 -g3 gcc options

[George Joseph (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-27563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=241420#comment-241420 ] 

George Joseph commented on ASTERISK-27563:
------------------------------------------

I NEVER use --enable-coverage

> Build process ignores DONT_OPTIMIZE and always sets -O3 -g3 gcc options
> -----------------------------------------------------------------------
>
>                 Key: ASTERISK-27563
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27563
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/BuildSystem
>    Affects Versions: 13.18.5, GIT, 15.1.5
>            Reporter: George Joseph
>
> Somehow the DONT_OPTIMIZE process got messed up and we're always setting -O3 -g3 on gcc command lines.  The -O3 probably isn't too bad but -g3 adds a ton of debugging symbols to what should be a production release.
> {noformat}
> $ ls -al main/asterisk
> -rwxrwxr-x. 1 gtjoseph gtjoseph 14615664 Jan  8 06:27 main/asterisk
> $ strip -g main/asterisk
> $ ls -al main/asterisk
> -rwxrwxr-x. 1 gtjoseph gtjoseph 3128432 Jan  8 06:30 main/asterisk
> {noformat}
> We should also use -ggdb3 instead of just -g3 to get gdb extensions which include macro processing.   Actually, we should ALWAYS compile with -ggdb3 and then do a strip on the binaries during install if DON"T OPTIMIZE wasn't set.  Actually, actually, we should probably change DONT_OPTIMIZE so it only controls -O and create a new option for STRIP_DEBUG that defaults to yes for non-dev-mode builds.



--
This message was sent by Atlassian JIRA
(v6.2#6252)