[asterisk-bugs] [JIRA] (ASTERISK-27722) [patch] BuildSystem: Depend not implicitly but explicitly on external libraries.

[Chris Savinovich (JIRA)]

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

Chris Savinovich updated ASTERISK-27722:
----------------------------------------

    Target Release Version/s: 13.21.0

> [patch] BuildSystem: Depend not implicitly but explicitly on external libraries.
> --------------------------------------------------------------------------------
>
>                 Key: ASTERISK-27722
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27722
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/BuildSystem, Resources/res_odbc
>    Affects Versions: 13.19.2, 15.2.2
>            Reporter: Alexander Traud
>            Assignee: Alexander Traud
>            Severity: Minor
>              Labels: patch
>      Target Release: 13.21.0
>
>         Attachments: odbc_explicit_depend.patch
>
>
> When an Asterisk module uses a symbol of an external library, it should declare is dependency explicitly. This avoids issues like in commit [eb0c9c4|http://github.com/asterisk/asterisk/commit/eb0c9c476f77701c693d68fe8d39508027b8f62f]. Furthermore, when that dependency is not declared explicitly, the created shared library does not load/link to that external library directly but via a dependency graph. That graph is created 'somehow' by the underlying platform and/or the load order and is therefore not reliable.
> For example, while testing under NetBSD 7, my Run Path (rpath) was wrong. Consequently, five modules did not load because their implicit dependency was not fulfilled. They all use at least one SQL_ symbol. This created several dozen messages on the Command Line Interface (CLI) of Asterisk. This was confusing as it hid the actual issue, the wrong Run Path.



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