[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [avr-gcc-list] AVRStudio and AVR GCC 3.3

From: David Brown
Subject: Re: [avr-gcc-list] AVRStudio and AVR GCC 3.3
Date: Thu, 5 Jun 2003 09:53:07 +0200

At the risk of re-openning old sores, the "clock skew detected" error is due
to Win9x being incapable of getting file time-stamps correct.  The stamps
can be a bit inaccurate (up to a few seconds, IIRC), leading make to get
confused over object files that were built in the future, or that are older
than the source files even after it has just recompiled them.  Waiting a few
seconds after saving your code before starting the make can sometimes help,
and it is sometimes useful to do a complete clean and re-build.

For the rest, give us a list of the files in your project (*not* the files
themselves), and a copy of your makefile.  Maybe we can spot the problem.



> Hello,
> I am trying to write a program for the ATMega16 using AVRStudio and
> 3.3 (which comes with WinAVR).  I have followed the instructions in the
> Readme file, but still I get errors.  I am testing the compiler with a
> simple program, I'm pretty sure there's no problems with that.  But here
> what I've got (in file temp.c):
> #include <avr/io.h>
> unsigned int var;
> int main (void) {
> for(;;) {
> var++;
> }
> }
> I've got everything set up right in the makefile; the makefile, gcc.bat,
> gcc2.bat, temp.c and temp project file in the project; the targets all and
> clean are set up and the settings have been configured (gcc.bat clean and
> gcc.bat all); and when I build clean, I get lots of lines saying "rm -f
> temp.---" where --- is replaced by different extensions each time.  At the
> end, it says:
> Errors: none
> ------ end ------
> make.exe *** Warning: clock skew detected.  Your build may be incomplete.
> Errors detected during link stage
> Stopped
> And the make.exe line doesn't always appear.
> Then when I build the all target,
> I get: make.exe *** No rule to make target `foo.o', needed by `temp.elf'.
> Stop.
> How can I fix this?
> Thanks,
> Jack

reply via email to

[Prev in Thread] Current Thread [Next in Thread]