I have tried to install the above package it builds but fails to install Reproducible: Always
Created attachment 200475 [details] build.log
Created attachment 200477 [details] emerge --info
have you emerged kdedevplatform?
No. I will try. But in this case this is a bug in the ebuild. kdedevplatform is not mentioned in the DEPEND nor th RDEPEND section in the ebuild.
That aint so big problem. Problem is this: -- JAVA_AWT_LIB_PATH: -- JAVA_JVM_LIB_PATH: -- JAVA_INCLUDE_PATH: JAVA_INCLUDE_PATH-NOTFOUND -- JAVA_INCLUDE_PATH2: JAVA_INCLUDE_PATH2-NOTFOUND -- JAVA_AWT_INCLUDE_PATH: JAVA_AWT_INCLUDE_PATH-NOTFOUND -- JAVA_JVM_LIBRARY: JAVA_JVM_LIBRARY-NOTFOUND it cant find java...
The problem is still valid with 4.3.3
Hmm, seems to work fine here (kde-4.4.0). -- using FindJNI.cmake -- JAVA_HOME: /etc/java-config-2/current-system-vm -- JAVA_AWT_LIB_PATH: -- JAVA_JVM_LIB_PATH: -- JAVA_INCLUDE_PATH: /etc/java-config-2/current-system-vm/include -- JAVA_INCLUDE_PATH2: /etc/java-config-2/current-system-vm/include/linux -- JAVA_AWT_INCLUDE_PATH: /etc/java-config-2/current-system-vm/include -- JAVA_JVM_LIBRARY: /etc/java-config-2/current-system-vm/jre/lib/amd64/server/libjvm.so -- Build Kross Java... yes
Created attachment 219917 [details] Output of emerge --info
same thing with 4.4.1
(In reply to comment #9) > same thing with 4.4.1 > Meaning, it works/installs or it does not work/does not install? please clarify!
(In reply to comment #10) > (In reply to comment #9) > > same thing with 4.4.1 > > > > Meaning, it works/installs or it does not work/does not install? please > clarify! > seems to install fine now, nevermind. (comp has apparently mood swings...)
OK, let's assume it is fixed in 4.4.x then. Please reopen if you disagree.
I just got bit by this on kde-base/krossjava-4.4.4, but I seem to have gotten around it. Running emerge with sudo didn't work. Running with "su -c" worked. Probably because sudo clears the environment, including the JAVA* variables, while su doesn't.
(In reply to comment #13) > I just got bit by this on kde-base/krossjava-4.4.4, but I seem to have gotten > around it. > > Running emerge with sudo didn't work. Running with "su -c" worked. Probably > because sudo clears the environment, including the JAVA* variables, while su > doesn't. > That is, however, not how it should work. Emerge should be independent from the user environment. Reopening...
This is portage or java-config bug and we (gentoo kde folks) can't really do anything about it. It's similar issue as those related to boost or python - anything using eselect. User needs to ensure correct (and what's important) - any java is enabled and present in environment - so source /etc/profile may be needed before running emerge.
(In reply to comment #15) > This is portage or java-config bug and we (gentoo kde folks) can't really do > anything about it. Accepted. > It's similar issue as those related to boost or python - anything using > eselect. > User needs to ensure correct (and what's important) - any java is enabled and > present in environment - so source /etc/profile may be needed before running > emerge. > The problem is, that while java is enabled and in the environment, sudo wipes the environment before running the command. Sourcing /etc/profile won't help. What will help is adding the various JAVA* variables to the env_keep in the sudoers file. I added the following to sudoers: Defaults:%portage env_keep += "JAVAC JAVACC_HOME JAVA_HOME JDK_HOME" and was able to emerge krossjava. The problem I see with this, is that it is using the users vm instead of the system vm for the install. Not a big issue for me (they're the same), but it could be for others.
*** Bug 323223 has been marked as a duplicate of this bug. ***
Should be solved by proper use of the java eclasses. I'll try during the next days....
Fixed in the overlay, please test.
(In reply to comment #19) > Fixed in the overlay, please test. > I had to add an export to the JAVA_HOME variable to get it to work. src_configure() { mycmakeargs=(-DENABLE_KROSSJAVA=ON) + export JAVA_HOME=$(java-config -g JAVA_HOME) kde4-meta_src_configure java-ant-2_src_configure }
(In reply to comment #20) > (In reply to comment #19) > > Fixed in the overlay, please test. > > > > I had to add an export to the JAVA_HOME variable to get it to work. > Hmm, strange. Well I guess it can't hurt. Added in overlay.
Fixed in 4.3.3, 4.3.5 and 4.4.4. Thanks for all involved!
exporting JAVA_HOME in src_configure doesn't fix it. Just hit it with 4.6.0
Created attachment 261417 [details] build.log Build log for 4.6.0
i was able to reproduce with dev-java/ibm-jdk-bin-1.6.0.9, it compiles fine with icedtea6 though
(In reply to comment #24) > Created an attachment (id=261417) [details] > build.log > > Build log for 4.6.0 > As I see it is a completely unrelated probem (ebuild doesn't find the kdepimlibs). So please open a new bugreport for this.
(In reply to comment #25) > i was able to reproduce with dev-java/ibm-jdk-bin-1.6.0.9, it compiles fine > with icedtea6 though > What was ibm-jdk-bin and icedtea6? The system java-vm, user java-vam, both?
(In reply to comment #26) > As I see it is a completely unrelated probem (ebuild doesn't find the > kdepimlibs). So please open a new bugreport for this. No, ignore the kdepimlibs warnings, the important part is the following, and I am able to reproduce it: -- Could NOT find JNI (missing: JAVA_JVM_LIBRARY JAVA_INCLUDE_PATH2) -- using FindKrossJNI.cmake -- JAVA_HOME: /opt/ibm-jdk-bin-1.6.0.9 -- JAVA_AWT_LIB_PATH: -- JAVA_JVM_LIB_PATH: -- JAVA_INCLUDE_PATH: /opt/ibm-jdk-bin-1.6.0.9/include -- JAVA_INCLUDE_PATH2: JAVA_INCLUDE_PATH2-NOTFOUND -- JAVA_AWT_INCLUDE_PATH: /opt/ibm-jdk-bin-1.6.0.9/include -- JAVA_JVM_LIBRARY: JAVA_JVM_LIBRARY-NOTFOUND (In reply to comment #27) > What was ibm-jdk-bin and icedtea6? The system java-vm, user java-vam, both? How can I see that? java n00b here
We could need some help from the java team here.
please provide output of `java-config -L` as root
(In reply to comment #20) > (In reply to comment #19) > > Fixed in the overlay, please test. > > > > I had to add an export to the JAVA_HOME variable to get it to work. > > src_configure() { > mycmakeargs=(-DENABLE_KROSSJAVA=ON) > + export JAVA_HOME=$(java-config -g JAVA_HOME) > kde4-meta_src_configure > java-ant-2_src_configure > } This shouldnt be needed actually kde4-meta eclass' pkg_setup is shadowing java's where all initilization of java eclass takes place.
(In reply to comment #31) > This shouldnt be needed actually kde4-meta eclass' pkg_setup is shadowing > java's where all initilization of java eclass takes place. pkg_preinst is shadown as well
thank you Serkan and everyone else involved fix was committed by Jonathan, closing