samba-bugs at samba.org
2014-Jul-14 08:51 UTC
[Bug 10715] New: IPv6 configure test fails on musl c-library
https://bugzilla.samba.org/show_bug.cgi?id=10715 Summary: IPv6 configure test fails on musl c-library Product: rsync Version: 3.1.1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at samba.org ReportedBy: timo.teras at iki.fi QAContact: rsync-qa at samba.org The autoconfigure tests for IPv6 relies on C-library internals, and it currently fails for musl c-library based linux. For Alpine Linux bug report see http://bugs.alpinelinux.org/issues/3158. A better test (and non-OS dependent) would be to try creating AF_INET6 socket, if it succeeds, then IPv6 is supported. See e.g.: http://ftp.netbsd.org/pub/NetBSD/NetBSD-release-6/src/crypto/dist/ipsec-tools/configure.ac (and search for --disable-ipv6) -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
samba-bugs at samba.org
2017-Sep-04 21:09 UTC
[Bug 10715] IPv6 configure test fails on musl c-library
https://bugzilla.samba.org/show_bug.cgi?id=10715 Pierre-Olivier Mercier <nemunaire at nemunai.re> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nemunaire at nemunai.re --- Comment #1 from Pierre-Olivier Mercier <nemunaire at nemunai.re> --- Created attachment 13546 --> https://bugzilla.samba.org/attachment.cgi?id=13546&action=edit Proposed patch to fix the issue Please find attached a proposal patch following Timo's suggestion: I replace the long specific C library detection (which in our case forgot musl's users) by a single feature test that all C libraries have to implement in order to have a compiling rsync with IPv6 support. After applying this patch, I was able to compile an IPv6 ready rsync with musl, while keeping the same behaviour with the glibc under Linux. This should be tested against others libc I don't have access to. -- You are receiving this mail because: You are the QA Contact for the bug.