On 30.10.18 11:29, Sebastian Smolorz wrote:
Fix linking error when using glibc versions which do not provide recvmmsg or sendmmsg.Signed-off-by: Sebastian Smolorz <sebastian.smol...@gmx.de> --- lib/cobalt/wrappers.c | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/lib/cobalt/wrappers.c b/lib/cobalt/wrappers.c index 20ad63a..951cd15 100644 --- a/lib/cobalt/wrappers.c +++ b/lib/cobalt/wrappers.c @@ -260,7 +260,11 @@ __weak int __real_recvmmsg(int fd, struct mmsghdr *msgvec, unsigned int vlen, unsigned int flags, struct timespec *timeout) { +#if (__GLIBC__ == 2) && (__GLIBC_MINOR__ < 12) + return -ENOSYS; +#else return recvmmsg(fd, msgvec, vlen, flags, timeout); +#endif }__weak@@ -273,7 +277,11 @@ __weak int __real_sendmmsg(int fd, struct mmsghdr *msgvec, unsigned int vlen, unsigned int flags) { +#if (__GLIBC__ == 2) && (__GLIBC_MINOR__ < 14) + return -ENOSYS; +#else return sendmmsg(fd, msgvec, vlen, flags); +#endif }__weak
Shouldn't we rather probe for the availability of such functions during configure? Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux
