AVR-Chat

Great idea.  I did not thnk of that myself,  but it was suggested to 
me before.  When I heard that suggestion I was POSITIVE that it was 
the problem.  Unfortunately it is NOT the case.  I scoured my 
computer for another make program.  Did not find one.  I was STILL so 
sure that I deleted the entire path except the winavr references.  No 
difference.

I still suspect that make is confused by the fact that it does not 
reside on the C drive, and it expects to be there in some basic way.

-Tony

--- In AVR-Chat@yahoogroups.com, Dave Hylands <dhylands@g...> wrote:
> Hi Tony,
> 
> > My path is:
> > 
> > %SYSTEMROOT%\system32;%SYSTEMROOT%;%SYSTEMROOT%\system32
> > \WBEM;F:\winavr\bin;F:\winavr\utils\bin;C:\PROGRA~1\ATITEC~1
> > \ATICON~1;C:\Program Files\ATI Technologies\ATI Control Panel
> 
> It sounds like there's a make.exe that's in one of these 
directories:
> %SYSTEMROOT%\system32
> %SYSTEMROOT%;%SYSTEMROOT%\system32\WBEM
> F:\winavr\bin
> 
> and it's not compatible with the make that comes with WinAVR.
> 
> Putting the make.exe into the "current" directory causes the correct
> one to be executed.
> 
> Try removing the make.exe and try this instead:
> 
> f:\winavr\utils\bin\make
> 
> iIf that works and typing make by itself doesn't, then there's 
almost
> certainly another make earlier in your path.
> 
> -- 
> Dave Hylands
> Vancouver, BC, Canada
> http://www.DaveHylands.com/