This is exactly the same issue as discussed in http://bugs.gentoo.org/335947 . Seems like the upstream patch wasn't introduced in the 1.18.3 release; the fix is the same, but the line numbers differ. here's the updated patch: --- coreutils/date.c 2011-02-08 17:24:57.000000000 +0000 +++ coreutils/date1.c 2011-04-01 01:31:26.000000000 +0000 @@ -249,7 +249,7 @@ int date_main(int argc UNUSED_PARAM, cha xstat(filename, &statbuf); ts.tv_sec = statbuf.st_mtime; #if ENABLE_FEATURE_DATE_NANO - ts.tv_nsec = statbuf.st_mtim.tv_nsec; + ts.tv_nsec = statbuf.st_mtimensec; /* some toolchains use .st_mtimensec instead of st_mtim.tv_nsec */ #endif } else {
Created attachment 269353 [details, diff] Patch without bugzilla damage. Note that bugzilla will destroy patches that are posted in the comment field, so here's the same patch as an attachment.
*** Bug 367235 has been marked as a duplicate of this bug. ***
*** Bug 380535 has been marked as a duplicate of this bug. ***
*** Bug 405231 has been marked as a duplicate of this bug. ***
Created attachment 302887 [details, diff] busybox-1.19.4-date_nano.patch I have created a patched ebuild of sys-apps/busybox-1.19.4 which fixes this - can be found in overlay: https://gitorious.org/abraxas-gentoo-overlay/abraxas-gentoo-overlay Patch is also attatched, please note that changing statbuf.st_mtim.tv_nsec to st_mtimensec without checks will break glibc.
latest uclibc + busybox seem to build fine together