From: Mike Sander <msander@ripnet.com>
To: buildroot@busybox.net
Subject: [Buildroot] $(DATE) out of sync with system
Date: Fri, 09 May 2008 12:34:09 -0400 [thread overview]
Message-ID: <48247D01.9030009@ripnet.com> (raw)
In-Reply-To: <000601c8b1ed$8d50afe0$070514ac@atmel.com>
Ulf Samuelsson wrote:
>> I have Custom rootfs suffix set to the default $(DATE). I have noticed
>> that a few hours before midnight my rootfs.arm-yyyymmdd.romfs, the dd
>> portion advances prematurely. this breaks a script I have to copy
>> binaries after the build.
>>
>> I suspect it is somehow related to DATE not using the timezone correctly
>> (maybe I dont have it set correctly?). I have attempted to find where
>> DATE is being set. I would imaging that it is using the "date" function
>> & format specifiers. Unfortunately DATE is a VERY common symbol under
>> buildroot. I am unable to locate where this symbol is initially set.
>>
>> Can someone tell me where to look?
>>
>>
>
>
> Top Makefile
>
Thanks. I had done a multi level grep for "DATE" and "="..... but this
generated literally hundreds of lines of output..... that proverbial
needle in the hay stack.
The relevant line does the following DATE:= $(shell date -u +%Y%m%d).
Anyone know why the "-u" which specifies Coordinated Universal Time?
This explains the rollover I see a few hours before midnight. Would it
not make more sense for this just to be local time? FWIW... I can
update my script to be consistent with the DATE logic now that I know
what is going on.
Regards,
Mike
> Best Regards
> Ulf Samuelsson
>
>
>
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Scanned with Copfilter Version 0.84beta3a (P3Scan 2.2.1)
> AntiSpam: SpamAssassin 3.2.3
> by Markus Madlener @ http://www.copfilter.org
>
>
next prev parent reply other threads:[~2008-05-09 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 2:27 [Buildroot] $(DATE) out of sync with system Mike Sander
2008-05-09 10:14 ` Ulf Samuelsson
2008-05-09 16:34 ` Mike Sander [this message]
2008-05-11 6:52 ` Ulf Samuelsson
2008-05-12 11:57 ` Mike Sander
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48247D01.9030009@ripnet.com \
--to=msander@ripnet.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox