Bug 6747 - [Build Appliance] gmp-native failed to do_compile
Summary: [Build Appliance] gmp-native failed to do_compile
Status: RESOLVED DUPLICATE of bug 5087
Alias: None
Product: Runtime
Classification: Build System, Metadata & Runtime
Component: build-appliance (show other bugs)
Version: 1.7
Hardware: x86 Multiple
: Undecided normal
Target Milestone: ---
Assignee: Cristian Iorga
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2014-09-23 02:47 UTC by Yi Zhao
Modified: 2014-09-23 13:04 UTC (History)
4 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: Regression (Used to work)
Verified:
Documentation change: No (bug/feature does not impact docs)


Attachments
log.do_compile (3.13 KB, application/octet-stream)
2014-09-23 02:47 UTC, Yi Zhao
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Yi Zhao 2014-09-23 02:47:26 UTC
Created attachment 2136 [details]
log.do_compile

Image Location: http://autobuilder.yoctoproject.org/pub/nightly/20140916-2/build-appliance/

Git rev: 7d80f8e9468253496a7097685aac8f468940a9c5

Steps:
1. Boot up BA in VM
2. Build a minimal image with qemumips

Error message:
#####################
checking whether build environment is sane... configure: error: newly created file is older than distributed files!
Check your system clock
Makefile:791: recipe for target 'config.status' failed
make: *** [config.status] Error 1
#####################
Comment 1 Yi Zhao 2014-09-23 08:08:14 UTC
I re-tested it and the issue disappeared. Maybe it is a VM system clock issue.
Comment 2 Cristian Iorga 2014-09-23 13:03:09 UTC
I have encountered this issue some time ago.
Details in: https://bugzilla.yoctoproject.org/show_bug.cgi?id=5087

It seems that (back than) I wrongly concluded the issue was fixed.

It appears the issue is transient and very hard to reproduce.

I will reopen the original bug report and make this a duplicate, as it has more details.
Comment 3 Cristian Iorga 2014-09-23 13:04:41 UTC
Duplicate issue.

*** This bug has been marked as a duplicate of bug 5087 ***