Recent changes have attempted to make consistant use of /etc/timestamp
In particular
  5aab665 initscripts: Make /etc/timestamp consistent again.
  173a48f image.bbclass: Ensure timestamp matches format used in initscripts 
after recent changes

This new format can cause problems as the value is too large for
most [32 bit] machines.  Work around this by only comparing the
YYYYMMDD portion (which does fit in 32 bits).  Also, the new format
is not directly compatible with the 'date' command line, so it
must be reformatted for use.

Signed-off-by: Gary Thomas <[email protected]>
---
 .../initscripts/initscripts-1.0/bootmisc.sh        |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-core/initscripts/initscripts-1.0/bootmisc.sh 
b/meta/recipes-core/initscripts/initscripts-1.0/bootmisc.sh
index 20ec0a0..383de82 100755
--- a/meta/recipes-core/initscripts/initscripts-1.0/bootmisc.sh
+++ b/meta/recipes-core/initscripts/initscripts-1.0/bootmisc.sh
@@ -70,8 +70,8 @@ if test -e /etc/timestamp
 then
        SYSTEMDATE=`date -u +%4Y%2m%2d%2H%2M`
        read TIMESTAMP < /etc/timestamp
-       if [ ${TIMESTAMP} -gt $SYSTEMDATE ]; then
-               date -u $TIMESTAMP
+       if [ ${TIMESTAMP%????} -gt ${SYSTEMDATE%????} ]; then
+               date -u ${TIMESTAMP#????}${TIMESTAMP%????????}
                /etc/init.d/hwclock.sh stop
        fi
 fi
-- 
1.7.7.6


_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Reply via email to