New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR installing java modular interface on cygwin #1146
Comments
Hey, I'll try to reproduce it and find a way around tomorrow. |
Hey, sorry for that long delay. I can reproduce the error on my machine. Will attempt to fix it. |
@grilomoto could you test this now with the new cmake build system |
I uninstalled and reinstalled the whole cygwin(java and javac commands were both working). Then I've tried to install the shogun version that is available to download in the site again, and the result was the following(from the part where it check for Java): grilomoto@grilomoto-PC ~/shogun-2.1.0/src !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ./configure --disable-svm-light The SVMlight license can be found in LICENSE.SVMlight. In case SHOGUN was configured for libshogun and the following interfaces: cmdline_static python_static octave_static octave_modular python_modular lua_modular interface(s) with the following configure options It will support the following data types bool,char,uint8_t,uint16_t,int32_t,int64_t,uint64_t,float32_t,float64_t. type "make" now to compile When I try to configure explicitly to Java(apparently Java ain't configured because shogun can not find Java includes...): grilomoto@grilomoto-PC ~/shogun-2.1.0/src Error: could not find java includes Check configure.log if you do not understand why it failed.
ldd ./configure-10138-6120.o Result is: yes ============ Checking for libshogun ============ ============ Checking for Java ============ ============ Checking for Java native interface files (jni.h) ============ Then I downloaded the develop branch from github as suggested by @vigsterkr and followed the "GENERAL" instructions in the "INSTALL" file. And that was the result(the cmake part was ok but the make had an error): grilomoto@grilomoto-PC ~/shogun-develop/src grilomoto@grilomoto-PC ~/shogun-develop/src src/shogun/CMakeFiles/version.dir/build.make:52: recipe for target |
@grilomoto thanks for getting back to us so soon! so what you would need to run cmake build with the develop branch:
could you copy-paste the output of this if there's still an error |
grilomoto@grilomoto-PC ~ grilomoto@grilomoto-PC ~ grilomoto@grilomoto-PC ~/shogun grilomoto@grilomoto-PC ~/shogun grilomoto@grilomoto-PC ~/shogun/build -- Configuring incomplete, errors occurred! |
do you have the full java SDK installed?
but of course in your case i don't know where the JAVA_HOME actually is |
I do have the full JDK but it is on windows (cygwin don't have java it uses the one on windows). ok i will try to set JAVA_HOME as soon as i find its path for cygwin through windows... |
I've set JAVA_HOME and the error stood the same |
where's your libawt.so and libjvm.so ? or i guess it would be libjvm.dll and libjvm.dll on windows... |
Sorry for the time it took for me to answer, I was reinstalling java as well as cygwin and resetting all of the environment variables related to java... And the same error happens again. There is no libawt or libjvm, there is however a awt.dll and a jvm.dll. And they are both in jre\bin whose path already is on the class_path. |
i have just installed all of the cygwin and am trying to install shogun.
at first i had the error:
Checking for Java ... 1.7.0_21
Checking for Java native interface files (jni.h) ... javac not detected
i've tested javac on cygwin and noticed that cygwin wasn't recognizing javac then i've used:
export PATH=$PATH:"/cygdrive/C/Program Files/Java/jdk1.6.0_23/bin/"
and cygwin started to recognyze javac but i still have the error:
Checking for Java ... 1.7.0_21
Checking for Java native interface files (jni.h) ... dirname: extra operand
Files' Try
dirname --help' for more information.Error: could not find java includes
and i can not find a way to solve this issue
The text was updated successfully, but these errors were encountered: