OpenWRT rebuilds the whole userspace from scratch and uses recent versions of tools and libraries, thus it should not be necessary in general to support CONFIG_COMPAT_32BIT_TIME, not even for purely 32bit systems: their updated userspace components should be fine with only 64bit time_t.
As OpenWRT is used as a base for embedded products for the future market it is the right default to set. Several targets enable this selectively, probably some of them should consider disabling it and see what happens. Cc: Arnd Bergmann <[email protected]> Signed-off-by: Linus Walleij <[email protected]> --- target/linux/generic/config-5.10 | 1 + 1 file changed, 1 insertion(+) diff --git a/target/linux/generic/config-5.10 b/target/linux/generic/config-5.10 index 120d1d8c3f4a..024d65ba7c8d 100644 --- a/target/linux/generic/config-5.10 +++ b/target/linux/generic/config-5.10 @@ -939,6 +939,7 @@ CONFIG_CMDLINE="" CONFIG_COMPACTION=y # CONFIG_COMPAL_LAPTOP is not set # CONFIG_COMPAT is not set +# CONFIG_COMPAT_32BIT_TIME is not set # CONFIG_COMPAT_BRK is not set # CONFIG_COMPILE_TEST is not set # CONFIG_CONFIGFS_FS is not set -- 2.29.2 _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
