[oe-issues] [Bug 2964] New: save-rtc date format causes error if busybox # CONFIG_FEATURE_DATE_ISOFMT is not set

[bugzilla-daemon at tinman.treke.net]

http://bugs.openembedded.org/show_bug.cgi?id=2964

           Summary: save-rtc date format causes error if busybox #
                    CONFIG_FEATURE_DATE_ISOFMT is not set
           Product: Openembedded
           Version: Angstrom
          Platform: ARM
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Build
        AssignedTo: openembedded-issues at lists.openembedded.org
        ReportedBy: sakoman at gmail.com


With the default config for busybox date (uclibc angstrom build), when
save-rtc.sh writes the time stamp file it ends up as: %2m%2d%2H%2M00%4Y rather
than a valid date.

It seems that without the CONFIG_FEATURE_DATE_ISOFMT flag set, busybox date
cannot handle numerics in the date format.

Possible fixes:

- Enable CONFIG_FEATURE_DATE_ISOFMT in the default busybox config
- Change the format in save-rtc from %2m%2d%2H%2M00%4Y to %m%d%H%M%Y (tested
only on uclibc build)
- Let each machine affected override save-rtc.sh


-- 
Configure bugmail: http://bugs.openembedded.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.