On Mon, 2012-01-23 at 17:32 +0100, Jelmer Vernooij wrote: > The whole point of this code block is to define IOV_MAX if the system > doesn't have it - other code relies on that constant. This change > breaks that contract. > > I see that POSIX doesn't mandate IOV_MAX if there is no maximum. I think > we should perhaps remove that error altogether (and change the contract) > and fix any calling code that has an absolute dependency on IOV_MAX, > rather than special casing GNU here.
Thanks, that would of course be the best solution. Are you both Debian maintainer and upstream author? Which parts of the software has the dependency on IOV_MAX? It seems that tdb does not. What about ldb and tevent you mentioned in your previous mail? -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
