Strange problem with a project.
-
@jsulm said in Strange problem with a project.:
@jenya7 said in Strange problem with a project.:
What is VCS
Version Control System
no. I don't use it. is it related to the problem?
-
@jsulm said in Strange problem with a project.:
@jenya7 said in Strange problem with a project.:
What is VCS
Version Control System
no. I don't use it. is it related to the problem?
@jenya7 said in Strange problem with a project.:
is it related to the problem?
Not directly, but it would make sure that date/time are correct.
On which file system is your project located? It is a Linux file system (like ext3)?
And how did you copy to Linux? -
@jenya7 said in Strange problem with a project.:
is it related to the problem?
Not directly, but it would make sure that date/time are correct.
On which file system is your project located? It is a Linux file system (like ext3)?
And how did you copy to Linux?@jsulm said in Strange problem with a project.:
@jenya7 said in Strange problem with a project.:
is it related to the problem?
Not directly, but it would make sure that date/time are correct.
On which file system is your project located? It is a Linux file system (like ext3)?
And how did you copy to Linux?It's Debian for RaspberryPi (Raspbian). I copy-paste the code to files created with QtCreator Installed on Linux.
-
when I build a project on a Linux machine I get
*.cpp has modification time 390886 s in the future.
Clock skew detected. Your build may be incomplete.@jenya7 said in Strange problem with a project.:
*.cpp has modification time 390886 s in the future.
Clock skew detected. Your build may be incomplete.This means your Windows and Linux PCs have different times. At least one of them is wrong.
For the Makefile system to work correctly, all of your files must have the correct "modified date" timestamps.
-
@jenya7 said in Strange problem with a project.:
*.cpp has modification time 390886 s in the future.
Clock skew detected. Your build may be incomplete.This means your Windows and Linux PCs have different times. At least one of them is wrong.
For the Makefile system to work correctly, all of your files must have the correct "modified date" timestamps.
@JKSH said in Strange problem with a project.:
@jenya7 said in Strange problem with a project.:
*.cpp has modification time 390886 s in the future.
Clock skew detected. Your build may be incomplete.This means your Windows and Linux PCs have different times. At least one of them is wrong.
For the Makefile system to work correctly, all of your files must have the correct "modified date" timestamps.
But how do I set those timestamps?
-
@JKSH said in Strange problem with a project.:
@jenya7 said in Strange problem with a project.:
*.cpp has modification time 390886 s in the future.
Clock skew detected. Your build may be incomplete.This means your Windows and Linux PCs have different times. At least one of them is wrong.
For the Makefile system to work correctly, all of your files must have the correct "modified date" timestamps.
But how do I set those timestamps?
@jenya7 I'm assuming the RasPi was never connected to the internet so the system time was never set properly. You can just connect your RasPi to the internet and it should auto update the system time. You should look into use github (or something else similar to it) to keep track of your code and it makes it easy to pull code onto different devices.
-
@JKSH said in Strange problem with a project.:
@jenya7 said in Strange problem with a project.:
*.cpp has modification time 390886 s in the future.
Clock skew detected. Your build may be incomplete.This means your Windows and Linux PCs have different times. At least one of them is wrong.
For the Makefile system to work correctly, all of your files must have the correct "modified date" timestamps.
But how do I set those timestamps?
-
@jenya7 I'm assuming the RasPi was never connected to the internet so the system time was never set properly. You can just connect your RasPi to the internet and it should auto update the system time. You should look into use github (or something else similar to it) to keep track of your code and it makes it easy to pull code onto different devices.
@vmanso said in Strange problem with a project.:
@jenya7 I'm assuming the RasPi was never connected to the internet so the system time was never set properly. You can just connect your RasPi to the internet and it should auto update the system time. You should look into use github (or something else similar to it) to keep track of your code and it makes it easy to pull code onto different devices.
Indeed at some point I disconnected it from internet (was testing internal LAN). Now I connected it back but still the same warning.
-
@vmanso said in Strange problem with a project.:
@jenya7 I'm assuming the RasPi was never connected to the internet so the system time was never set properly. You can just connect your RasPi to the internet and it should auto update the system time. You should look into use github (or something else similar to it) to keep track of your code and it makes it easy to pull code onto different devices.
Indeed at some point I disconnected it from internet (was testing internal LAN). Now I connected it back but still the same warning.
This post is deleted! -
@jsulm said in Strange problem with a project.:
@jenya7 said in Strange problem with a project.:
But how do I set those timestamps?
man touch
Thank you. It helps. Did it for every file. Now it compiles OK.
