Thanks for the info. I have been using cmd.exe. I have also been trying to use make with the Programmers Notepad. Both techniques fail in the same way. Make tries to run, but it fails. I quadruple checked the path. It is fine. I even moved the winavr references to the front of the path. I even deleted all the rest of the path EXCEPT the winavr stuff. No change. I then deleted the entire path. In this case make could not be found. I then moved make into the current (demo) directory. Then make WORKED FINE. So, it has someting to do with the path, but I do not know what. I am running winavr from my F: drive, not the C: drive. Maybe this has something to do with it. I may have to move the winavr directory to the c: drive and test it there. Any ideas why the path would not work right? -Tony --- In AVR-Chat@yahoogroups.com, Dave Hylands <dhylands@g...> wrote: > > Quick way to find out what make is running type "make -v" in a > > command.com window to see what it says. No where near my WinAVR system > > but it should look something like this: > > You should only be using command.com (which is a 16 bit shell) if > you're using Win9x. If you're using WinNT/2K/XP, you'll be much better > off using cmd.exe (whihch is a 32 bit shell). I set mine up to have a > virtual window that's 9999 rows high and 160 columns wide. Then you > can scroll back through old output and whatnot. > > -- > Dave Hylands > Vancouver, BC, Canada > http://www.DaveHylands.com/
Message
Re: Problem using MAKE - still no good
2005-04-12 by arhodes19044
Attachments
- No local attachments were found for this message.