Yes . But this difference we expect in some minutes.
But what i am observing is ( attached snapshot ) :- 1) First Compilation around ( 4:10) bitbake cleanall + bitbake core-image-minimal uname-a : Time shown is 4:24 timestamp of files in deploy/images/ : Time shown is around 4:30 2) Second Compilation around ( 5:00) bitbake -c menuconfig virtual/kernel + bitbake -C deploy linux-yocto uname-a : Time shown is 4:24 timestamp of files in deploy/images/ : Time shown is around 5:25 2) Second Compilation around ( 5:00) bitbake -c menuconfig virtual/kernel + bitbake -C deploy linux-yocto uname-a : Time shown is 4:24 timestamp of files in deploy/images/ : Time shown is around 5:25 3) Third Compilation around ( 5:45) bitbake -c menuconfig virtual/kernel + bitbake -C deploy linux-yocto uname-a : Time shown is 4:24 timestamp of files in deploy/images/ : Time shown is around 6:05 So , time shown by "uname -a" is retains older value even though i had compiled the linux multiple times . Currently , only way i am able to bypass this behavior is to do bitbake -c cleanall linux-yocto before every compilation. Thanks Ashish On Fri, May 10, 2019 at 10:23 PM Khem Raj <raj.k...@gmail.com> wrote: > > > On 5/10/19 12:10 AM, AshishKumar Mishra wrote: > > HI Anuj , > > > > I was building minimal image using $ bitbake core-image-minimal haven't > > tried full-cmdline. > > > > Not able to track why kernel "uname" has older timestamp rather than > > the one from build/deploy/image > > as seen by "ls -al <build/deploy/image> > > > > Am i missing any command or sequence here > > > > > > uname will show the time when it was built, which might be different > time then the one when it was copied over to deploy. >
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto