On Fri, 2007-10-05 at 08:25 +0200, Pierre Ossman wrote: > Print a warning or something so that they can be found. Don't go > breaking systems left and right. People have better things to do than > to fix the build systems for ever program they use.
The kernel knows bugger all about what glibc function your program is calling. The problem here is precisely that newer versions of glibc will transform legacy 32-bit stat() calls into 64-bit stat64() calls, then will complain when the result overflows. If you want to figure out which apps are broken, then you will have to either do so in glibc or use a preloaded shared library to intercept the 32-bit stat() calls and print out a warning. Trond - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
