[asterisk-bugs] [JIRA] (ASTERISK-28374) latest asterisk unconditionally launch gcc --version, even if the compiler is different
Asterisk Team (JIRA)
noreply at issues.asterisk.org
Wed May 22 13:52:49 CDT 2019
[ https://issues.asterisk.org/jira/browse/ASTERISK-28374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Asterisk Team updated ASTERISK-28374:
-------------------------------------
Target Release Version/s: 16.4.0
> latest asterisk unconditionally launch gcc --version, even if the compiler is different
> ---------------------------------------------------------------------------------------
>
> Key: ASTERISK-28374
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-28374
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Core/BuildSystem
> Affects Versions: 13.26.0, 16.3.0
> Environment: Any where main compiler is named differently than gcc, but there is also gcc 8.x around.
> Encountered in the FreeBSD port.
> Reporter: Guido Falsi
> Assignee: Guido Falsi
> Severity: Minor
> Target Release: 16.4.0, 13.27.0
>
>
> In latest asterisk a check for GCC version has been added. It is performed by unconditionally running "gcc --version".
> If the main compiler being used is another one (F.E. cc) this check will test the wrong compiler and add compiler flags which may be incorrect.
> On FreeBSD the main compiler is clang, named cc. When gcc 8 is installed on the system, this check will return true, and add a compiler flag which is refused by clang, causing the build to fail.
> I'm going to propose a review on gerrit patching the Makefile to perform the check using the $(CC) variable, containing the actual compiler being used for the build.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list