Re: Problems installing JDK 1.5
We've seen JVM lockups during high contention Threading operations with the jdk15 port. The same code succeeded when running under diablo-jdk. I have precious little information on the details of the failure we saw so I'm hesitant to toss the jdk15 port squarely under the bus without more poking at the issue, but time just isn't on my side lately. :) Perhaps this will jog the memories of others who can elaborate. Juergen Nickelsen wrote: Stefan Walter [EMAIL PROTECTED] writes: It might be easier for you to just use the java/diablo-jdk15 port, which installs precompiled binaries. Although I have, with the much appreciated help from people here, successfully installed the jdk15 port in between, I thought about diablo-jdk15, too. Would there be any difference between both ports in terms of compatibility, features, and performance from the viewpoint of the Java developer and user? -- Sam Baskinger Software Engineer Lumeta - Securing the Network in the Face of Change www.lumeta.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems installing JDK 1.5
Stefan Walter wrote: Hi, Bill Smith, 06.03.07, 18:25h CET: I have been having problems with this as well, I have the linprocfs mounted, but the buil is dying with the following error: ../../../src/share/classes/sun/net/www/protocol/http/HttpURLConnection.java:1186 : warning: non-varargs call of varargs method with inexact argument type for las t parameter; cast to java.lang.Object for a varargs call cast to java.lang.Object[] for a non-varargs call and to suppress this warning return (IOException)ctr.newInstance(args); ^ ../../../src/share/classes/com/sun/jmx/mbeanserver/StandardMetaDataImpl.java:637 : warning: non-varargs call of varargs method with inexact argument type for las t parameter; cast to java.lang.Object for a varargs call cast to java.lang.Object[] for a non-varargs call and to suppress this warning result = meth.invoke(instance,null); ^ ../../../src/share/classes/com/sun/jmx/mbeanserver/MBeanInstantiatorImpl.java:16 2: warning: non-varargs call of varargs method with inexact argument type for la st parameter; cast to java.lang.Object for a varargs call cast to java.lang.Object[] for a non-varargs call and to suppress this warning moi= cons.newInstance(null); ^ Note: * uses or overrides a deprecated API. Note: Recompile with -Xlint:deprecation for details. Note: Some input files use unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details. 21 errors 12 warnings gmake[3]: *** [.compile.classlist] Error 1 gmake[3]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make/java/java' gmake[2]: *** [all] Error 1 gmake[2]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make/java' gmake[1]: *** [all] Error 1 gmake[1]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make' gmake: *** [j2se-build] Error 2 *** Error code 2 Stop in /usr/ports/java/jdk15. The warnings about varargs are harmless. The errors causing the build to fail seem to have happened earlier and are not listed here. It might be easier for you to just use the java/diablo-jdk15 port, which installs precompiled binaries. Cheers Stefan, I have done that and all is now ok -- Bill ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems installing JDK 1.5
Hi, Bill Smith, 06.03.07, 18:25h CET: I have been having problems with this as well, I have the linprocfs mounted, but the buil is dying with the following error: ../../../src/share/classes/sun/net/www/protocol/http/HttpURLConnection.java:1186 : warning: non-varargs call of varargs method with inexact argument type for las t parameter; cast to java.lang.Object for a varargs call cast to java.lang.Object[] for a non-varargs call and to suppress this warning return (IOException)ctr.newInstance(args); ^ ../../../src/share/classes/com/sun/jmx/mbeanserver/StandardMetaDataImpl.java:637 : warning: non-varargs call of varargs method with inexact argument type for las t parameter; cast to java.lang.Object for a varargs call cast to java.lang.Object[] for a non-varargs call and to suppress this warning result = meth.invoke(instance,null); ^ ../../../src/share/classes/com/sun/jmx/mbeanserver/MBeanInstantiatorImpl.java:16 2: warning: non-varargs call of varargs method with inexact argument type for la st parameter; cast to java.lang.Object for a varargs call cast to java.lang.Object[] for a non-varargs call and to suppress this warning moi= cons.newInstance(null); ^ Note: * uses or overrides a deprecated API. Note: Recompile with -Xlint:deprecation for details. Note: Some input files use unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details. 21 errors 12 warnings gmake[3]: *** [.compile.classlist] Error 1 gmake[3]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make/java/java' gmake[2]: *** [all] Error 1 gmake[2]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make/java' gmake[1]: *** [all] Error 1 gmake[1]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make' gmake: *** [j2se-build] Error 2 *** Error code 2 Stop in /usr/ports/java/jdk15. The warnings about varargs are harmless. The errors causing the build to fail seem to have happened earlier and are not listed here. It might be easier for you to just use the java/diablo-jdk15 port, which installs precompiled binaries. Regards, Stefan pgpsxiisvUC5P.pgp Description: PGP signature
Re: Problems installing JDK 1.5
Stefan Walter [EMAIL PROTECTED] writes: It might be easier for you to just use the java/diablo-jdk15 port, which installs precompiled binaries. Although I have, with the much appreciated help from people here, successfully installed the jdk15 port in between, I thought about diablo-jdk15, too. Would there be any difference between both ports in terms of compatibility, features, and performance from the viewpoint of the Java developer and user? -- I don't know anything about music. In my line you don't have to. -- Elvis Presley ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems installing JDK 1.5
Sam Baskinger wrote: Juergen Nickelsen wrote: On Feb 27 2007, Chris Timmons wrote: Don't forget that the linux JDK will want you to have linprocfs mounted. I recently had a similar build experience of jdk-1.5.0p4 which cleared up fine after I remembered about linprocfs. linprocfs /compat/linux/proc linprocfs rw 0 0 Hm. I cannot imagine how this could lead to the problems I saw, but another thing to try. Thanks! Linux systems store tons of need-to-know data in the /proc file system. If you've ever installed a chrooted Linux environment you must 'mount -o bind' the /proc file system from the running system to the chroot for many OS functions to work correctly. I suspect that Java was looking for some process information in linprocfs and since it wasn't mounted, it blew up. :) Hope this clears up the why question. :) I have been having problems with this as well, I have the linprocfs mounted, but the buil is dying with the following error: ../../../src/share/classes/sun/net/www/protocol/http/HttpURLConnection.java:1186 : warning: non-varargs call of varargs method with inexact argument type for las t parameter; cast to java.lang.Object for a varargs call cast to java.lang.Object[] for a non-varargs call and to suppress this warning return (IOException)ctr.newInstance(args); ^ ../../../src/share/classes/com/sun/jmx/mbeanserver/StandardMetaDataImpl.java:637 : warning: non-varargs call of varargs method with inexact argument type for las t parameter; cast to java.lang.Object for a varargs call cast to java.lang.Object[] for a non-varargs call and to suppress this warning result = meth.invoke(instance,null); ^ ../../../src/share/classes/com/sun/jmx/mbeanserver/MBeanInstantiatorImpl.java:16 2: warning: non-varargs call of varargs method with inexact argument type for la st parameter; cast to java.lang.Object for a varargs call cast to java.lang.Object[] for a non-varargs call and to suppress this warning moi= cons.newInstance(null); ^ Note: * uses or overrides a deprecated API. Note: Recompile with -Xlint:deprecation for details. Note: Some input files use unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details. 21 errors 12 warnings gmake[3]: *** [.compile.classlist] Error 1 gmake[3]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make/java/java' gmake[2]: *** [all] Error 1 gmake[2]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make/java' gmake[1]: *** [all] Error 1 gmake[1]: Leaving directory `/usr/ports/java/jdk15/work/j2se/make' gmake: *** [j2se-build] Error 2 *** Error code 2 Stop in /usr/ports/java/jdk15. any offers? -- Bill ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems installing JDK 1.5
- Juergen Nickelsen [EMAIL PROTECTED] wrote: ... But indeed I was ignorant of the diablo port. What is the relation between these two ports anyway? I do not really get the difference, in spite of http://www.freebsdfoundation.org/downloads/java.shtml. ... There are some license restrictions on distribution of jdk binaries. In order to be distributable, jdk binaries need to pass Sun's test suite (TCK). So the Diablo binary passes, and is distributation. The port, is just source, and does not require testing. A binary built from the port may or may not pass, depending on the current state of development. There can be regressions as things change in the OS, and linked in packages. The jdk has a fair number of dependencies, so it is pretty easy to blow-up a jdk build. Some of the developers on the FreeBSD java list have the TCK, and can tell if you if the port would pass the TCK. And you should really be asking about this on the FreeBSD java list, as they are constantly making changes to the port, and dependencies. Tom ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems installing JDK 1.5
On 07. Mrz 2007, at 8:12, Tom Samplonius wrote: There are some license restrictions on distribution of jdk binaries. In order to be distributable, jdk binaries need to pass Sun's test suite (TCK). So the Diablo binary passes, and is distributation. The port, is just source, and does not require testing. A binary built from the port may or may not pass, depending on the current state of development. There can be regressions as things change in the OS, and linked in packages. The jdk has a fair number of dependencies, so it is pretty easy to blow-up a jdk build. I see. Thanks for the clarification! Regards, Juergen. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems installing JDK 1.5
Juergen Nickelsen [EMAIL PROTECTED] writes: On Tue, Feb 27, 2007 at 11:22:44AM -0500, Sam Baskinger wrote: I'm assuming that you installed linux compatibility and then the linux-jdk 1.4? I failed to do that and saw a very similar error a while back. :) That may well be the case. I assumed the port installed it as a dependency, but I didn't really look close. Thanks for the hint! I'll report back later. It was indeed the Linux compatibility bits missing [1], including, of course, the linprocfs. Why this caused syntax errors while compiling Java code is beyond me, though. Thanks for the help! -- The most likely way for the world to be destroyed, most experts agree, is by accident. That's where we come in. We're computer professionals. We cause accidents.-- Nathaniel Borenstein ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems installing JDK 1.5
Dan Nelson [EMAIL PROTECTED] writes: You could also install the native diablo-jdk15 port instead of a Linux one. I was installing the native port /usr/ports/java/jdk15, only it needs the Linux JDK 1.4.2 to compile the Java sources. But indeed I was ignorant of the diablo port. What is the relation between these two ports anyway? I do not really get the difference, in spite of http://www.freebsdfoundation.org/downloads/java.shtml. -- I object to doing things that computers can do.-- Olin Shivers ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems installing JDK 1.5
On Feb 27 2007, Chris Timmons wrote: Don't forget that the linux JDK will want you to have linprocfs mounted. I recently had a similar build experience of jdk-1.5.0p4 which cleared up fine after I remembered about linprocfs. linprocfs /compat/linux/proc linprocfs rw 0 0 Hm. I cannot imagine how this could lead to the problems I saw, but another thing to try. Thanks! Regards, Juergen. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems installing JDK 1.5
Juergen Nickelsen wrote: On Feb 27 2007, Chris Timmons wrote: Don't forget that the linux JDK will want you to have linprocfs mounted. I recently had a similar build experience of jdk-1.5.0p4 which cleared up fine after I remembered about linprocfs. linprocfs /compat/linux/proc linprocfs rw 0 0 Hm. I cannot imagine how this could lead to the problems I saw, but another thing to try. Thanks! Linux systems store tons of need-to-know data in the /proc file system. If you've ever installed a chrooted Linux environment you must 'mount -o bind' the /proc file system from the running system to the chroot for many OS functions to work correctly. I suspect that Java was looking for some process information in linprocfs and since it wasn't mounted, it blew up. :) Hope this clears up the why question. :) Sam Baskinger Lumeta - Securing the Network in the Face of Change www.lumeta.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems installing JDK 1.5
I did not have any problems with 5.5 however I started by installing Tomcat and everything else need was installed . I usualy compile my ports by hand and updated them by ctm. (getting deltas) regards, wlodek - Original Message - From: Juergen Nickelsen [EMAIL PROTECTED] lsen.de Newsgroups: w21.lists.freebsd-stable To: [EMAIL PROTECTED] d.org Sent: Monday, February 26, 2007 4:37 PM Subject: Problems installing JDK 1.5 Hello, on a more or less newly installed machine with 5.5-STABLE (updated recently) I tried to install JDK 1.5 via /usr/ports/. After retrieving all necessary files, the build failed quite mysteriously, even more so as I had succeeded with another machine fine last year. In the build protocol the problems seem to begin like this: Java HotSpot(TM) Client VM warning: Can't detect initial thread stack location /usr/ports/java/jdk15/work/control/build/bsd-i586/gensrc/sun/nio/cs/St = andardChar\ sets.java:226: identifier expected and then a series of other errors in the Java code; as if it is compiled using the wrong compiler version. It looks weird to me, as I think I fetched the correct files and did everything as carefully as last year. Is this a known problem? Does anyone know a way around it? Is the port currently broken, perhaps? Details can be found in [3]http://www.schlabun.org/screenlog.2; and I'll gladly provide more details if necessary. Regards, Juergen. ___ [EMAIL PROTECTED] rg mailing list [5]h= ttp://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] References 1. 3Dmailto:[EMAIL PROTECTED] 2. 3Dmailto:freebsd-stable@freebsd.org; 3. 3Dhttp://www.schlabun.org/screenl 4. 3Dmailto:freebsd-stable@freebsd.org; 5. 3Dhttp://lists.freebsd.org/mailman/listinfo/freebsd-stable; 6. 3Dmailto:freebsd-stable-uns___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems installing JDK 1.5
I'm assuming that you installed linux compatibility and then the linux-jdk 1.4? I failed to do that and saw a very similar error a while back. :) Sam Baskinger Lumeta - Securing the Network in the Face of Change www.lumeta.com Juergen Nickelsen wrote: Hello, on a more or less newly installed machine with 5.5-STABLE (updated recently) I tried to install JDK 1.5 via /usr/ports/. After retrieving all necessary files, the build failed quite mysteriously, even more so as I had succeeded with another machine fine last year. In the build protocol the problems seem to begin like this: Java HotSpot(TM) Client VM warning: Can't detect initial thread stack location /usr/ports/java/jdk15/work/control/build/bsd-i586/gensrc/sun/nio/cs/StandardChar\ sets.java:226: identifier expected and then a series of other errors in the Java code; as if it is compiled using the wrong compiler version. It looks weird to me, as I think I fetched the correct files and did everything as carefully as last year. Is this a known problem? Does anyone know a way around it? Is the port currently broken, perhaps? Details can be found in http://www.schlabun.org/screenlog.2; and I'll gladly provide more details if necessary. Regards, Juergen. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems installing JDK 1.5
On Tue, Feb 27, 2007 at 11:22:44AM -0500, Sam Baskinger wrote: I'm assuming that you installed linux compatibility and then the linux-jdk 1.4? I failed to do that and saw a very similar error a while back. :) That may well be the case. I assumed the port installed it as a dependency, but I didn't really look close. Thanks for the hint! I'll report back later. Regards, Juergen. [...] Juergen Nickelsen wrote: Hello, on a more or less newly installed machine with 5.5-STABLE (updated recently) I tried to install JDK 1.5 via /usr/ports/. After retrieving all necessary files, the build failed quite mysteriously, even more so as I had succeeded with another machine fine last year. In the build protocol the problems seem to begin like this: -- Never trust an operating system you don't have sources for. -- Joerg Wunsch ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems installing JDK 1.5
In the last episode (Feb 27), Juergen Nickelsen said: On Tue, Feb 27, 2007 at 11:22:44AM -0500, Sam Baskinger wrote: I'm assuming that you installed linux compatibility and then the linux-jdk 1.4? I failed to do that and saw a very similar error a while back. :) That may well be the case. I assumed the port installed it as a dependency, but I didn't really look close. Thanks for the hint! I'll report back later. You could also install the native diablo-jdk15 port instead of a Linux one. -- Dan Nelson [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems installing JDK 1.5
Don't forget that the linux JDK will want you to have linprocfs mounted. I recently had a similar build experience of jdk-1.5.0p4 which cleared up fine after I remembered about linprocfs. linprocfs /compat/linux/proc linprocfs rw 0 0 -Chris On Tue, 27 Feb 2007, Juergen Nickelsen wrote: On Tue, Feb 27, 2007 at 11:22:44AM -0500, Sam Baskinger wrote: I'm assuming that you installed linux compatibility and then the linux-jdk 1.4? I failed to do that and saw a very similar error a while back. :) That may well be the case. I assumed the port installed it as a dependency, but I didn't really look close. Thanks for the hint! I'll report back later. Regards, Juergen. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Problems installing JDK 1.5
Hello, on a more or less newly installed machine with 5.5-STABLE (updated recently) I tried to install JDK 1.5 via /usr/ports/. After retrieving all necessary files, the build failed quite mysteriously, even more so as I had succeeded with another machine fine last year. In the build protocol the problems seem to begin like this: Java HotSpot(TM) Client VM warning: Can't detect initial thread stack location /usr/ports/java/jdk15/work/control/build/bsd-i586/gensrc/sun/nio/cs/StandardChar\ sets.java:226: identifier expected and then a series of other errors in the Java code; as if it is compiled using the wrong compiler version. It looks weird to me, as I think I fetched the correct files and did everything as carefully as last year. Is this a known problem? Does anyone know a way around it? Is the port currently broken, perhaps? Details can be found in http://www.schlabun.org/screenlog.2; and I'll gladly provide more details if necessary. Regards, Juergen. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
