Hi! > Some distributions (RHEL5, for instance) don't have defined utimensat() > system call. So I introduced an autoconf check for this, otherwise > safe_file_ops.c can > not be compiled on these distributions. > > Actually, I'm not satisfied with > utimes(pathname, NULL) > because it throws away the time-changing logic from safe_touch(). > > How do you think it is safe to explicitly define UTIME_* constants in LTP > sources (safe_file_ops.h): > > #ifndef UTIME_NOW > #define UTIME_NOW ((1l << 30) - 1l) > #endif > > #ifndef UTIME_OMIT > #define UTIME_OMIT ((1l << 30) - 2l) > #endif
Any progress on this? Do you need a help? The latest git build on older distros is broken and should be fixed ASAP... -- Cyril Hrubis [email protected] ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk _______________________________________________ Ltp-list mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ltp-list
