perusing the glibc source and headers it seems to come down to the
#undef __IOV_MAX
line in bits/uio_lim.h.
The Changelog (2017-06-14) speaks rather obliquely to the issue, but I
can't quite figure out if
sysconf(_SC_IOV_MAX);
now returning -1 (errno = 0) is an unintentional side effect of the
changes or not. (I don't follow glibc development to know what the
history is behind this change.) In f26, glibc-2.25-10 it returns 1024.
Off hand I don't see any way that glibc could be built now to make the
call return anything but -1.
Anyone know more of the story? Or want to venture a guess?
Thanks
--
Kaleb
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
