[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=230961#comment-230961 ] 

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

I have not tested this with Fedora, but instead of {{memset}} what happens when you go for just one zero, like the following:{noformat}{ {0,} };{noformat}

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