I recently built findutils 4.6.0 on a DEC/Compaq/HP[E] Tru64 system with imperfect results:
urtx# touch fred urtx# /usr/local/bin/find . -name fred -printf '%C+\n' %F+13:28:57.0000000000 My (quick, unreliable) analysis suggests that this is caused by use of the (old/lame) Tru64 strftime(), which does not support "%F". The findutils "configure" script seems to think that any old strftime() is good enough: checking for strftime... yes urtx# grep -i strftime config.h /* Define to 1 if you have the `strftime' function. */ #define HAVE_STRFTIME 1 /* Define to the name of the strftime replacement function. */ #define my_strftime nstrftime But this one apparently isn't. Interestingly, the findutils kit includes a (gl/lib/) strftime.c, but it seems to be built with special options to provide nstrftime() (and strftime_case_()?), but not a plain GNU strftime(), which seems to be needed here. Should the findutils builders (or I) be more clever, or should I have a whole GNU run-time library (with a better strftime()) available independently, or is Tru64 just too old to be tolerated nowadays, or what? urtx# uname -a OSF1 urtx.antinode.info V5.1 2650 alpha urtx# sizer -v HP Tru64 UNIX V5.1B (Rev. 2650); Wed Feb 17 22:59:59 CST 2016 urtx# /usr/sbin/dupatch -track -type patch_level | grep -i 'patch kit' Gathering details of relevant patch kits... Patch Kit 5: T64V51BB26AS0005-20050502 OSF540 Patch Kit 6: T64V51BB27AS0006-20061208 OSF540 Patch Kit 7: T64V51BB28AS0007-20090312 OSF540 Patch Kit 8: T64V51BB29AS0008-20100821 OSF540 urtx# gcc -v Using built-in specs. Target: alphaev6-dec-osf5.1b Configured with: ../gcc-4.3.2/configure --enable-languages=c,c++,objc,obj-c++,treelang Thread model: posix gcc version 4.3.2 (GCC) urtx# /usr/local/bin/find --version find (GNU findutils) 4.6.0 [...] If more information would be helpful, then please let me know. Thanks. ------------------------------------------------------------------------ Steven M. Schweda sms@antinode-info