On Fri, 19 Aug 2016, Zack Weinberg wrote: > I'd feel a lot safer about changing the default if we had some way of > tagging object files and shared libraries so that _FILE_OFFSET_BITS=32 > and _FILE_OFFSET_BITS=64 code could not be combined. Do we already have But combining such files is fine if _FILE_OFFSET_BITS is not part of the ABI for those libraries (and there are plenty of libraries for which that's the case, even if they should be using _FILE_OFFSET_BITS=64 internally). My view is that changing the default is better then the status quo where distributions provide libraries compiled with a mixture of _FILE_OFFSET_BITS settings and users need to match the setting for a given library where it's part of the ABI. The change should rapidly lead to very few people using _FILE_OFFSET_BITS=32 (but making that into just a glibc-internal "don't redirect functions in headers" mode for compiling the glibc compat versions of functions for old binaries, rather than supporting _FILE_OFFSET_BITS=32 for users, would be harder). -- Joseph S. Myers joseph@xxxxxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
