"clock skew detected. Your build is may be incomplete"
309 views
Skip to first unread message
Eren Basturk
unread,
Jun 3, 2014, 10:53:53 AM6/3/14
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to machi...@googlegroups.com
Hi All,
When I compile src files , I get the below error.
"clock skew detected. Your build is may be incomplete"
for example: I setupped new image to BBB and ran it. next, I passed /home/machinekit/machinekit-dev/src directory after that I ran make command to compiling.
the compiling process complete with some warnings such as "clock skew detected. Your build is may be incomplete" error. Maybe I setupped the image 20 times.
even if I change many things in hal_pru_generic directory , the system works well because , the compiling process doesn't complete.
Do you think what is my problem?How can I solve this?
Best Regards
Charles Steinkuehler
unread,
Jun 3, 2014, 10:58:35 AM6/3/14
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Eren Basturk, machi...@googlegroups.com
Your local clock on the BeagleBone is probably not set correctly. The
'bone does not have an RTC, so if you don't have a network cable
connected it can't get the correct time.
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Eren Basturk, Machinekit Mailing List
Hi
This is normally simply your system clock being out.
If it is 1 hour behind, the time stamp on all the files can be in the
'future'.
As make looks to see if files have changed, source file time stamps
newer than the output binary for instance, it could lead to file changes
not getting compiled
Easiest answer, make clean then 'touch' the whole source tree and make again
(and check your system clock)