[asterisk-bugs] [JIRA] (ASTERISK-27681) [patch] BuildSystem: Enable IMAP storage on OpenBSD.

[Alexander Traud (JIRA)]

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

Alexander Traud updated ASTERISK-27681:
---------------------------------------

          Description: 
On OpenBSD 6.2, the library c-client ([UW IMAP Toolkit|http://en.wikipedia.org/wiki/UW_IMAP]), does not load its depended libraries itself. In other words: Although that library uses functions/symbols of OpenSSL/LibreSSL, the library does not load -lcrypto and -lssl automatically. Because of this, the script ./configure of Asterisk is not able to compile/link a small app to double-check the existence of the library -lc-client.

The attached patch adds those dependencies manually. No regression is expected, because c-client is linked with those two libraries on other platforms anyway. Here, we just link manually.

This patch is the same as the patch of the official port for OpenBSD. The cause and solution were found independently:
The script ./configure creates a log file _config.log_ which shows the created app and the result of compiling/linking. There, in that log several OpenSSL symbols were listed as missing by the tool _ld_. Tools like _ldd_ and _nm_ verify those findings on the shared library _libc-client.so_.

  was:
On OpenBSD 6.2, the library c-client, does not load its depended libraries itself. In other words: Although that library uses functions/symbols of OpenSSL/LibreSSL, the library does not load -lcrypto and -lssl automatically. Because of this, the script ./configure of Asterisk is not able to compile/link a small app to double-check the existence of the library -lc-client.

The attached patch adds those dependencies manually. No regression is expected, because c-client is linked with those two libraries on other platforms anyway. Here, we just link manually.

This patch is the same as the patch of the official port for OpenBSD. The cause and solution were found independently:
The script ./configure creates a log file _config.log_ which shows the created app and the result of compiling/linking. There, in that log several OpenSSL symbols were listed as missing by the tool _ld_. Tools like _ldd_ and _nm_ verify those findings on the shared library _libc-client.so_.

    External Issue ID: https://github.com/openbsd/ports/blob/master/telephony/asterisk/patches/patch-configure_ac

> [patch] BuildSystem: Enable IMAP storage on OpenBSD.
> ----------------------------------------------------
>
>                 Key: ASTERISK-27681
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27681
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_voicemail, Core/BuildSystem
>    Affects Versions: 13.19.1
>            Reporter: Alexander Traud
>            Severity: Minor
>              Labels: patch
>         Attachments: OpenBSD_enable_imap_storage.patch
>
>
> On OpenBSD 6.2, the library c-client ([UW IMAP Toolkit|http://en.wikipedia.org/wiki/UW_IMAP]), does not load its depended libraries itself. In other words: Although that library uses functions/symbols of OpenSSL/LibreSSL, the library does not load -lcrypto and -lssl automatically. Because of this, the script ./configure of Asterisk is not able to compile/link a small app to double-check the existence of the library -lc-client.
> The attached patch adds those dependencies manually. No regression is expected, because c-client is linked with those two libraries on other platforms anyway. Here, we just link manually.
> This patch is the same as the patch of the official port for OpenBSD. The cause and solution were found independently:
> The script ./configure creates a log file _config.log_ which shows the created app and the result of compiling/linking. There, in that log several OpenSSL symbols were listed as missing by the tool _ld_. Tools like _ldd_ and _nm_ verify those findings on the shared library _libc-client.so_.



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