[asterisk-bugs] [JIRA] (ASTERISK-26104) Build: A Fedora GLIBC update to 2.22-17 causes a compile failure
Richard Mudgett (JIRA)
noreply at issues.asterisk.org
Thu Jun 9 11:40:56 CDT 2016
[ https://issues.asterisk.org/jira/browse/ASTERISK-26104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Richard Mudgett updated ASTERISK-26104:
---------------------------------------
Description:
The Fedora update to GLIBC 2.22-17 change the order of the members in sockaddr_storage. Unfortunately there are a few places where we use an initializer for ast_sockaddr like '\{ \{ 0, 0 } }' which now fail.
They need to be changed to memsets.
was:
The Fedora update to GLIBC 2.22-17 change the order of the members in sockaddr_storage. Unfortunately there are a few places where we use an initializer for ast_sockaddr like '{ { 0, 0 } }' which now fails.
They need to be changed to memsets.
> Build: A Fedora GLIBC update to 2.22-17 causes a compile failure
> -----------------------------------------------------------------
>
> Key: ASTERISK-26104
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-26104
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Core/BuildSystem
> Affects Versions: SVN, 11.21.2, 13.9.1
> Reporter: George Joseph
> Assignee: George Joseph
>
> The Fedora update to GLIBC 2.22-17 change the order of the members in sockaddr_storage. Unfortunately there are a few places where we use an initializer for ast_sockaddr like '\{ \{ 0, 0 } }' which now fail.
> They need to be changed to memsets.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list