Re: [OpenWrt-Devel] Q: musl: ether_aton() behaves differently than in glibc

2018-07-01 Thread Zefir Kurtisi
On 06/30/2018 08:56 PM, Rosen Penev wrote: > On Wed, Jun 27, 2018 at 7:55 AM Zefir Kurtisi > wrote: >> >> Hi, >> >> I found a proprietary package stopped working after moving from glibc to >> musl and >> ended up identifying a difference in processing of ether_aton(). >> >> In musl, the

Re: [OpenWrt-Devel] Q: musl: ether_aton() behaves differently than in glibc

2018-06-30 Thread Rosen Penev
On Wed, Jun 27, 2018 at 7:55 AM Zefir Kurtisi wrote: > > Hi, > > I found a proprietary package stopped working after moving from glibc to musl > and > ended up identifying a difference in processing of ether_aton(). > > In musl, the ether_addr string is expected to be NULL terminated (see >

[OpenWrt-Devel] Q: musl: ether_aton() behaves differently than in glibc

2018-06-27 Thread Zefir Kurtisi
Hi, I found a proprietary package stopped working after moving from glibc to musl and ended up identifying a difference in processing of ether_aton(). In musl, the ether_addr string is expected to be NULL terminated (see https://git.musl-libc.org/cgit/musl/tree/src/network/ether.c#n20), while