mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox <barebox@lists.infradead.org>
Subject: Re: build timestamps don't work
Date: Fri, 18 May 2012 10:49:21 +0200	[thread overview]
Message-ID: <20120518084921.GP30400@pengutronix.de> (raw)
In-Reply-To: <CAA4bVAGhuekyOa5cjJHcWJUYm6K4SPn=c3BXTauFP3CvFaMX7A@mail.gmail.com>

On Fri, May 18, 2012 at 12:28:52AM +0400, Antony Pavlov wrote:
> On 17 May 2012 22:19, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> > On Thu, May 17, 2012 at 09:52:36PM +0400, Antony Pavlov wrote:
> >> ping
> >>
> >> On 16 May 2012 08:27, Antony Pavlov <antonynpavlov@gmail.com> wrote:
> >> > Hi!
> >> >
> >> >  I have found that on my Debian testing build system generation of
> >> > timestamps don't work correctly.
> >
> > I just tried and it works with ARM builds. Tried again with MIPS, and
> > yes, indeed it does not work. Maybe worth looking at the architecture
> > specific Makefile.
> >
> 
> I tried another debian linux. I tried ARM & MIPS: the both don't work.
> 
> I checked linux-3.1 build for mips: it work. At least  there is one differrence:
> in linux if i make 'rm .version && make', then scripts/mkcompile_h
> started _two_ times, but only _one_ time in barebox.

Just to make sure, you have the following in your tree, right?

commit 55c81081e577922a8d7d0a1d633efb7feb3560d4
Author: Sascha Hauer <s.hauer@pengutronix.de>
Date:   Sun Apr 15 12:05:21 2012 +0200

    Makefile: fix build timestamps
    
    This patch adds the scripts/mkcompile_h from the Kernel. This gives
    us additional information about the build like who built this binary
    and with which compiler. Currently the only information used is the
    build timestamp and the generation number.
    This also fixes the build timestamp in the banner which is now
correct
    even with consecutive builds without making clean in between.
    
    Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2012-05-18  8:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-16  4:27 Antony Pavlov
2012-05-17 17:52 ` Antony Pavlov
2012-05-17 18:19   ` Sascha Hauer
2012-05-17 18:24     ` Antony Pavlov
2012-05-17 20:28     ` Antony Pavlov
2012-05-18  8:49       ` Sascha Hauer [this message]
2012-05-18 10:50         ` Antony Pavlov

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=20120518084921.GP30400@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=antonynpavlov@gmail.com \
    --cc=barebox@lists.infradead.org \
    /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