23 Nov
2004
23 Nov
'04
2:04 p.m.
On Tue, 23 Nov 2004 12:13:22 +0100, Alexandre Julliard wrote:
No, that's only fixing a symptom. glibc simply doesn't support running on an older version than what it was compiled against; the problem is not limited to epoll, it can potentially happen with any symbol. The right way to build a package that runs on both old and new glibcs is to build it against the old one, anything else is asking for trouble.
... or bypassing glibc oddness entirely and using syscalls to work around it, as we do in a few other places in the source. I think that was discussed before and rejected though.