Summary: | ASTERISK-27112: Core/BuildSystem: Cannot compile with AST_DEVMODE & OpenSSL >= 1.1 | ||
Reporter: | Jean Aunis - Prescom (PrescomJA) | Labels: | |
Date Opened: | 2017-07-07 09:56:22 | Date Closed: | 2017-10-23 16:40:34 |
Priority: | Major | Regression? | |
Status: | Closed/Complete | Components: | Core/BuildSystem |
Versions: | 14.4.0 GIT | Frequency of Occurrence | Constant |
Related Issues: | |||
Environment: | Ubuntu 16.04, OpenSSL 1.1.0f | Attachments: | |
Description: | Since my last system update, Asterisk fails to compile when configured with AST_DEVMODE. This seems to be due to the new version of OpenSSL (1.1.0f).
Here is the error I get : {code} libasteriskssl.c:48:12: error: ‘startup_complete’ defined but not used [-Werror=unused-variable] static int startup_complete; ^ libasteriskssl.c:54:22: error: ‘ssl_threadid’ defined but not used [-Werror=unused-function] static unsigned long ssl_threadid(void) ^ libasteriskssl.c:59:13: error: ‘ssl_lock’ defined but not used [-Werror=unused-function] static void ssl_lock(int mode, int n, const char *file, int line) {code} I managed to work around this by adding a #ifdef around these definitions in asterisk/libasteriskssl.c. Problem found in both version 14.4.1 and latest Git revision. | ||
Comments: | By: Asterisk Team (asteriskteam) 2017-07-07 09:56:22.819-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Corey Farrell (coreyfarrell) 2017-10-23 16:40:34.717-0500 This was fixed by ASTERISK-27156. |