Closed acquarius1990 closed 10 years ago
Hi, we think we know what the problem with this is and we are implementing a fix right now. We are about to release a brand new version of gkno and we will incorporate the fix into this version. I will let you know when that version is available, but it should be in the next couple of days.
On Tue, Jan 14, 2014 at 1:05 PM, acquarius1990 notifications@github.comwrote:
[09:56 user@cluster gkno_launcher]$ ./gkno build
Boston College gkno package
version: 0.106
date: November 2013
Reading in command line arguments...done.
Checking dependencies...failed.
The following utilities have version numbers that could not be determined by gkno: javac
This indicates a likely bug or as-yet-unseen oddity. Please contact the gkno development team to report this issue. Thanks.
TERMINATED: Errors found in running gkno. See specific error messages above for resolution.
And here's info about my javac: javac -v
Eclipse Java Compiler 0.894_R34x, 3.4.2 release, Copyright IBM Corp 2000, 2008. All rights reserved.
— Reply to this email directly or view it on GitHubhttps://github.com/gkno/gkno_launcher/issues/8 .
Should be fixed with the latest update.
I just removed the check for 'javac' version number, since there's not really a good way to get it from Eclipse's output. Instead we'll just check that the utility exists. Since we're already checking the installed JRE ('java -version'), I feel like we should be safe in assuming the two are compatible.
Feel free to re-open the issue, @acquarius1990 or any future reader, if this assumption turns out to be incorrect.
[09:56 user@cluster gkno_launcher]$ ./gkno build
And here's info about my javac:
javac -v