Ah, I see. So it appears to be the Java path issue.
And no, I didn't mean that `make` itself depends on `uname`. I meant that ENIGMA's makefile depends on `uname`.
I believe we have a bug open on it here:
http://enigma-dev.org/tracker/ticket.php?id=48
The workaround, of course, is to run LGM from the command line in the appropriate directory. This has always been encouraged anyways, because the command line provides verbose feedback on errors and other issues that may arise while the projects are still young and bug-prone.
And no, I didn't mean that `make` itself depends on `uname`. I meant that ENIGMA's makefile depends on `uname`.
I believe we have a bug open on it here:
http://enigma-dev.org/tracker/ticket.php?id=48
The workaround, of course, is to run LGM from the command line in the appropriate directory. This has always been encouraged anyways, because the command line provides verbose feedback on errors and other issues that may arise while the projects are still young and bug-prone.
