[asterisk-bugs] [JIRA] (ASTERISK-24923) Enabling DONT_OPTIMIZE can cause link errors to be lost.

[Corey Farrell (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-24923?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Corey Farrell closed ASTERISK-24923.
------------------------------------

    Resolution: Won't Fix

I don't think this can be fixed.  To detect link errors you should build Asterisk twice, once with and once without DONT_OPTIMIZE.  If running the full build twice COMPILE_DOUBLE should be disabled as it would only make the build take longer.

> Enabling DONT_OPTIMIZE can cause link errors to be lost.
> --------------------------------------------------------
>
>                 Key: ASTERISK-24923
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24923
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/BuildSystem
>    Affects Versions: SVN, 11.16.0, 13.2.0
>            Reporter: Corey Farrell
>
> To see this issue in action, checkout trunk revision 433524.  Enable build of utils/aelparse.  Build with DONT_OPTIMIZE enabled will succeed, build with DONT_OPTIMIZE disabled will fail:
> {noformat}
>    [LD] aelparse.o aelbison.o pbx_ael.o hashtab.o lock.o ael_main.o ast_expr2f.o ast_expr2.o strcompat.o pval.o extconf.o -> aelparse
> hashtab.o: In function `_ast_calloc':
> include/asterisk/utils.h:568: undefined reference to `ast_log_safe'
> ...
> hashtab.o:include/asterisk/utils.h:568: more undefined references to `ast_log_safe' follow
> {noformat}
> This seems to be the case with or without AST_DEVMODE, it doesn't matter what other options are chosen, DONT_OPTIMIZE somehow causes the call to ast_log_safe to disappear.  I'm unsure how this is possible.
> Although these instructions are for testing against trunk I believe this issue applies to all branches.



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