Rockbox Development > Starting Development and Compiling

Compiling error since move to SVN

(1/2) > >>

rossic:
Hi,

I had been compiling from CVS with no problems until the switch to SVN.  I get strange warnings and errors since.

Here are the errors from a recent attempt:

make[1]: Warning: File `/cygdrive/d/Rockbox/Source/sim/sim/dep-sim' has modification time 1.1 s in the future
make[1]: warning:  Clock skew detected.  Your build may be incomplete.
make[1]: Warning: File `/cygdrive/d/Rockbox/Source/sim/comsim/dep-commonsim' has modification time 0.73 s in the future
make[1]: warning:  Clock skew detected.  Your build may be incomplete.
Header parsed
make[1]: Warning: File `/cygdrive/d/Rockbox/Source/sim/firmware/dep-firmware' has modification time 0.39 s in the future
Header parsed
make[1]: warning:  Clock skew detected.  Your build may be incomplete.
make[2]: Warning: File `/cygdrive/d/Rockbox/Source/sim/apps/bitmaps/native/dep-bitmaps-native' has modification time 1.2 s in the future
make[2]: warning:  Clock skew detected.  Your build may be incomplete.
make[2]: Warning: File `/cygdrive/d/Rockbox/Source/sim/apps/bitmaps/remote_native/dep-bitmaps-remotenative' has modification time 1.8 s in the future
make[2]: warning:  Clock skew detected.  Your build may be incomplete.
make[1]: Warning: File `/cygdrive/d/Rockbox/Source/sim/apps/dep-apps' has modification time 0.36 s in the future
make[1]: *** [/cygdrive/d/Rockbox/Source/sim/apps/lang.o] Error 53
make: *** [all] Error 2


At first I wanted to blame the build, but no one else seemed to be having issues.  Then I assumed SVN wasn't downloading all of the files properly (it would freeze while downloading a few times), but even with a tar ball I was getting the same errors (occasionally not finding apps/atoi.o).  Now I'm wondering if the install of SVN or TortoiseSVN has caused something to be misplaced.  Any suggestions ???

Thanks in advance  ;)

rossic:
Well, I figured out what was wrong with the warnings regarding Clock Skew.  Apparently it means nothing - just that FAT32 file structures are only specific to 2 seconds whereas cygwin is by millisecond.  Thus, Windows may occasionally jump ahead in the future when writing files.  If you run the compiler on NTFS, you will have no problems with Clock Skew.

However, I still get the following errors:

Header parsed
Header parsed
make[1]: *** [/home/rockbox/2007-01-21/build/apps/lang.o] Error 53
make: *** [all] Error 2

Any thoughts?

rossic:
Haha... Another post...

After a lot of searching, I found something strange.  I have attached the stdout and stderr output as a file.  

The last line (before it fails to compile) says:
"CC lang.c"  
and thus fails to build the lang.o file.

However, there is no "lang.c" file within the source.  There is also no "lang.h" file, but it is referenced in the "language.c" file.  Has there been some naming convention changed that was not updated in the auto build of the makefile?  Where is this lang.c file that I don't have?  

I imagine people are pretty crazy right now trying to restore the page, so I'll try to be patient for a few days...

Thanks

[attachment deleted by admin, too old]

Lear:
lang.c is generated during the build (the GENLANG step in the attached output) and should be available in the folder where you run make. Either lang.c, or the compiled lang.o, seem to be corrupt somehow. Try deleting them (or maybe even run 'make clean') and run make again.

You're correct about the clock skew thing, but the reason you get it is probably that when you updated Cygwin to get SVN, you got a newer version of make too, in which a work-around for this problem isn't enabled.

rossic:
Thanks for your quick and informative reply.  I was a little afraid that lang.c was generated on the fly because it's not generating it for me  :'(

I've cleaned, verycleaned, and made a few times.  

Don't know if it matters (because the tar ball doesn't work either) but I downloaded SVN from their website, not through cygwin's installer.  Maybe something else is out of date, and I should upgrade my packages anyway.  I'll give it a shot.  Thanks for the perspective.  

If you have any other info regarding GENLANG, and why it might fail me, I'd love to hear it.  

Navigation

[0] Message Index

[#] Next page