I have just set up devkitARM, according to the instructions on this webpage:
http://devkitpro.org/wiki/Getting_Started/devkitARM
When I attempt to compile the examples, however, I get the following output/error:
make[1]: Entering directory `/opt/devkitpro/examples/nds/audio'
make[2]: Entering directory `/opt/devkitpro/examples/nds/audio/maxmod'
make[3]: Entering directory `/opt/devkitpro/examples/nds/audio/maxmod/audio_modes'
/bin/sh: ndstool: not found
make[4]: *** [/opt/devkitpro/examples/nds/audio/maxmod/audio_modes/audio_modes.nds] Error 127
make[3]: *** [build] Error 2
make[3]: Leaving directory `/opt/devkitpro/examples/nds/audio/maxmod/audio_modes'
make[2]: *** [all] Error 1
make[2]: Leaving directory `/opt/devkitpro/examples/nds/audio/maxmod'
make[1]: *** [all] Error 1
make[1]: Leaving directory `/opt/devkitpro/examples/nds/audio'
make: *** [examples] Error 1
I get this error when I try to compile any other projects as well. I have already set my environment variables as it told me on the page I linked to. I am using Ubuntu 11.04, if that helps. Any help on fixing this would be appreciated!
ndstool Not found
-
- Site Admin
- Posts: 1986
- Joined: Tue Aug 09, 2005 3:21 am
- Location: UK
- Contact:
Re: ndstool Not found
Sorry, slight packaging problem with the i686 linux build of devkitARM.
I've just uploaded a fixed tarball for devkitARM release 33 and an archive of the i686-linux ndstool to https://sourceforge.net/projects/devkit ... devkitARM/
I've just uploaded a fixed tarball for devkitARM release 33 and an archive of the i686-linux ndstool to https://sourceforge.net/projects/devkit ... devkitARM/
Re: ndstool Not found
Thank you very much! I actually was able to get it to work using the windows build of ndstool and configuring it under WINE, but this is probably more stable, haha. Thanks.
-
- Site Admin
- Posts: 1986
- Joined: Tue Aug 09, 2005 3:21 am
- Location: UK
- Contact:
Re: ndstool Not found
That's nuts You could have just compiled ndstool from source, everything is in sourceforge SVN.
Not that it matters hugely now, I fixed this with devkitARM release 34
Not that it matters hugely now, I fixed this with devkitARM release 34
Who is online
Users browsing this forum: No registered users and 1 guest