[asterisk-bugs] [JIRA] (ASTERISK-26104) Build: A Fedora GLIBC update to 2.22-17 causes a compile failure

[Alexander Traud (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-26104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=230985#comment-230985 ] 

Alexander Traud commented on ASTERISK-26104:
--------------------------------------------

The curlies are because of ast_sockaddr which contains sockaddr_storage (and GCC is complaining about having to init both structs). The Zero is the standard initializer for a C struct. The rest of the Asterisk code does exactly this for ast_sockaddr: { {0,} }; and was not blamed by this issue here. The problem was this second zero. By the way, peercnt needs { { {0,} } }; because it is a struct with a struct with a struct.

> 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)