gbadev.org forum archive

This is a read-only mirror of the content originally found on forum.gbadev.org (now offline), salvaged from Wayback machine copies. A new forum can be found here.

DS development > Libnds / Devkitpro compile errors (nevermind!)

#165466 - Darkuna - Mon Dec 22, 2008 8:50 am

Okay, noob on windows trying to get into NDS programming here.

So I install devkitpro fresh, and go into the examples for nds installed with it, and every single one of them i try to use the make command for produces:

Error makefile 6: Command syntax error
Error makefile 7: Command syntax error
Error makefile 8: Command syntax error
Error makefile 10: Command syntax error
Error makefile 55: Command syntax error
Error makefile 71: Command syntax error
Error makefile 75: Command syntax error
Error makefile 79: Command syntax error
Error makefile 95: Command syntax error
Error makefile 96: Command syntax error
Error makefile 97: Command syntax error
Error makefile 106: Command syntax error
Error makefile 113: Colon expected
Error makefile 114: Colon expected
Error makefile 115: Colon expected
Error makefile 124: Command syntax error
Error makefile 127: Command syntax error
*** 17 errors during make ***

What the heck am I doing wrong? Nothing I try to make anywhere does anything but this, and I haven't changed anything to have broken it myself.

---

..And now they're gone. Just like that.
I didn't even do anything different, it just suddenly worked after many completely identical failures. Okay then! I'd still like to know wtf the problem was, but at least its' working now.

#165490 - wintermute - Tue Dec 23, 2008 2:10 am

Do you have Delphi or some other Borland tool installed?

This one is often caused by a make that isn't gnu make being in the path ahead of the msys make. Not sure why it would suddenly just work though.
_________________
devkitPro - professional toolchains at amateur prices
devkitPro IRC support
Personal Blog

#165523 - tepples - Wed Dec 24, 2008 2:37 pm

Perhaps everything started working once the environment variables propagated. Several things can cause that to happen: closing the command prompt and opening a new one, logging out and in, restarting Windows...
_________________
-- Where is he?
-- Who?
-- You know, the human.
-- I think he moved to Tilwick.