Re: jdk15 on 6.0
james g. escribió: After several failed attempts at the package route, this was certainly a welcome surprise: http://www.freebsdfoundation.org/downloads/java.shtml I have downloaded diablo-jre-freebsd6-1.5.0.06.00.tbz from the link above, ha, by the way i have a FreeBSD 6.1 box, when i try to install it i got this messages: pkg_add diablo-jre-freebsd6-1.5.0.06.00.tbz pkg_add: could not find package xorg-libraries-6.8.2 ! pkg_add: could not find package javavmwrapper-2.0_5 ! I dont want to install xorg- related libreries :( what are the steps to install java whitout X? Does anybody know where i can find a how to? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: jdk15 on 6.0
After several failed attempts at the package route, this was certainly a welcome surprise: http://www.freebsdfoundation.org/downloads/java.shtml Thanks to everyone for their help and suggestions! -james On Apr 3, 2006, at 12:55 PM, james g. wrote: Thanks everyone for the tips. I'm going to give the package route a shot, as the additional swap space just isn't cutting it. Cheers, James On Apr 3, 2006, at 8:14 AM, Jon Brisbin wrote: Anish Mistry wrote: You could always just to do a "make package" on another machine with 6.0 and then just pkg_add on your older system. This is what I did when I installed JDK 1.5 on our BSD boxes. It sounds like, with so little physical RAM, that the JVM is only allocating a very small percentage of that to the JVM that starts up when the build gets bootstrapped. The jvmg probably needs to be manually set using an -Xms/-Xmx value that will give it enough room to work with. To the JVM, swap space isn't the same as physical RAM. I have had problems running java applications that have to swap. With Java, physical RAM is crucial. If you could even put at least 512MB in that box just for the build, then take it out to run it, you would probably succeed. Barring that, you're next best bet is probably going to be building it on another box, then doing a pkg_add. -- Thanks! Jon Brisbin Webmaster NPC International, Inc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions- [EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions- [EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: jdk15 on 6.0
Thanks everyone for the tips. I'm going to give the package route a shot, as the additional swap space just isn't cutting it. Cheers, James On Apr 3, 2006, at 8:14 AM, Jon Brisbin wrote: Anish Mistry wrote: You could always just to do a "make package" on another machine with 6.0 and then just pkg_add on your older system. This is what I did when I installed JDK 1.5 on our BSD boxes. It sounds like, with so little physical RAM, that the JVM is only allocating a very small percentage of that to the JVM that starts up when the build gets bootstrapped. The jvmg probably needs to be manually set using an -Xms/-Xmx value that will give it enough room to work with. To the JVM, swap space isn't the same as physical RAM. I have had problems running java applications that have to swap. With Java, physical RAM is crucial. If you could even put at least 512MB in that box just for the build, then take it out to run it, you would probably succeed. Barring that, you're next best bet is probably going to be building it on another box, then doing a pkg_add. -- Thanks! Jon Brisbin Webmaster NPC International, Inc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions- [EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: jdk15 on 6.0
Anish Mistry wrote: You could always just to do a "make package" on another machine with 6.0 and then just pkg_add on your older system. This is what I did when I installed JDK 1.5 on our BSD boxes. It sounds like, with so little physical RAM, that the JVM is only allocating a very small percentage of that to the JVM that starts up when the build gets bootstrapped. The jvmg probably needs to be manually set using an -Xms/-Xmx value that will give it enough room to work with. To the JVM, swap space isn't the same as physical RAM. I have had problems running java applications that have to swap. With Java, physical RAM is crucial. If you could even put at least 512MB in that box just for the build, then take it out to run it, you would probably succeed. Barring that, you're next best bet is probably going to be building it on another box, then doing a pkg_add. -- Thanks! Jon Brisbin Webmaster NPC International, Inc. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: jdk15 on 6.0
On Sunday 02 April 2006 14:36, james g. wrote: > On Apr 2, 2006, at 11:41 AM, Andrew Pantyukhin wrote: > > On 4/2/06, james g. <[EMAIL PROTECTED]> wrote: > >> FreeBSD Land: > >> > >> I've seen this question asked on this very list, and once or > >> twice on the web, but have yet to find a solution. > >> > >> I'm attempting to compile jdk15 on an older machine, and at > >> first attempted it on a 4.11 install. The failures there > >> encouraged me to finally upgrade the machine to 6.0. > >> > >> So now, I have a fully patched, fresh 6.0 installation. The > >> machine has 128MB physical ram, and I doubled the default swap > >> space. When I continued to run into memory errors while > >> attempting to compile the jdk, I added an additional swap file > >> of 512MB. Even with all this additional swap space, I'm getting > >> the following compilation error every time: > >> > >> `/usr/ports/java/jdk15/work/control/build/bsd-i586/hotspot-i586/ > >>tmp/ bsd_i486_compiler2/jvmg' > >> gmake[3]: Entering directory > >> `/usr/ports/java/jdk15/work/control/ > >> build/bsd-i586/hotspot-i586/tmp/bsd_i486_compiler2/jvmg' > >> Compiling ../generated/adfiles/ad_i486.cpp > >> virtual memory exhausted: Cannot allocate memory > >> gmake[3]: *** [ad_i486.o] Error 1 > >> gmake[3]: Leaving directory `/usr/ports/java/jdk15/work/control/ > >> build/ > >> bsd-i586/hotspot-i586/tmp/bsd_i486_compiler2/jvmg' > >> gmake[2]: *** [the_vm] Error 2 > >> gmake[2]: Leaving directory `/usr/ports/java/jdk15/work/control/ > >> build/ > >> bsd-i586/hotspot-i586/tmp/bsd_i486_compiler2/jvmg' > >> gmake[1]: *** [jvmg] Error 2 > >> gmake[1]: Leaving directory `/usr/ports/java/jdk15/work/control/ > >> build/ > >> bsd-i586/hotspot-i586/tmp' > >> gmake: *** [jvmg] Error 2 > >> *** Error code 2 > >> > >> Stop in /usr/ports/java/jdk15. > >> > >> > >> Does jdk15 really require more swapspace? I don't making the > >> additional swap file larger, but pushing 1GB of swap already is > >> leading me to believe there is another cause. > >> > >> Any help is greatly appreciated, as I'd really like to get jdk15 > >> installed and running on this specific machine, despite it's > >> age. > >> > >> Cheers, > >> James > > > > AFAICT yes, it is possible that 1Gb (try 2Gb to be sure) swap > > will solve it. I can start trying to imagine how long it would > > take to compile jdk15, though. And even if you do succeed, an > > average java application can take about 100Mb of RAM > > right from the start. So you should really choose between a > > newer box and a sensible programming language. > > Thanks for the tip. I upped the additional swapfile size to 2GB and > tried again, with the same results. > > Granted I understand that expecting so much from this little > machine is really pushing it, it will eventually just be running a > small java- based server, that unfortunately requires jdk15. I > wouldn't ever choose it on purpose. > > With a total swap size of roughly 2.5GB still generating failures, > is this a lost cause, or should I be looking for additional > solutions? You could always just to do a "make package" on another machine with 6.0 and then just pkg_add on your older system. -- Anish Mistry pgpE8ZzGxZTxG.pgp Description: PGP signature
Re: jdk15 on 6.0
On 4/2/06, james g. <[EMAIL PROTECTED]> wrote: > Granted I understand that expecting so much from this little machine > is really pushing it, it will eventually just be running a small java- > based server, that unfortunately requires jdk15. I wouldn't ever > choose it on purpose. > > With a total swap size of roughly 2.5GB still generating failures, is > this a lost cause, or should I be looking for additional solutions? /usr/ports/java/linux-sun-jdk15/ perhaps? -- -- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: jdk15 on 6.0
james g. wrote: > > On Apr 2, 2006, at 11:41 AM, Andrew Pantyukhin wrote: > >> On 4/2/06, james g. <[EMAIL PROTECTED]> wrote: >>> FreeBSD Land: >>> >>> I've seen this question asked on this very list, and once or twice on >>> the web, but have yet to find a solution. >>> >>> I'm attempting to compile jdk15 on an older machine, and at first >>> attempted it on a 4.11 install. The failures there encouraged me to >>> finally upgrade the machine to 6.0. >>> >>> So now, I have a fully patched, fresh 6.0 installation. The machine >>> has 128MB physical ram, and I doubled the default swap space. When I >>> continued to run into memory errors while attempting to compile the >>> jdk, I added an additional swap file of 512MB. Even with all this >>> additional swap space, I'm getting the following compilation error >>> every time: >>> >>> `/usr/ports/java/jdk15/work/control/build/bsd-i586/hotspot-i586/tmp/ >>> bsd_i486_compiler2/jvmg' >>> gmake[3]: Entering directory `/usr/ports/java/jdk15/work/control/ >>> build/bsd-i586/hotspot-i586/tmp/bsd_i486_compiler2/jvmg' >>> Compiling ../generated/adfiles/ad_i486.cpp >>> virtual memory exhausted: Cannot allocate memory >>> gmake[3]: *** [ad_i486.o] Error 1 >>> gmake[3]: Leaving directory `/usr/ports/java/jdk15/work/control/build/ >>> bsd-i586/hotspot-i586/tmp/bsd_i486_compiler2/jvmg' >>> gmake[2]: *** [the_vm] Error 2 >>> gmake[2]: Leaving directory `/usr/ports/java/jdk15/work/control/build/ >>> bsd-i586/hotspot-i586/tmp/bsd_i486_compiler2/jvmg' >>> gmake[1]: *** [jvmg] Error 2 >>> gmake[1]: Leaving directory `/usr/ports/java/jdk15/work/control/build/ >>> bsd-i586/hotspot-i586/tmp' >>> gmake: *** [jvmg] Error 2 >>> *** Error code 2 >>> >>> Stop in /usr/ports/java/jdk15. >>> >>> >>> Does jdk15 really require more swapspace? I don't making the >>> additional swap file larger, but pushing 1GB of swap already is >>> leading me to believe there is another cause. >>> >>> Any help is greatly appreciated, as I'd really like to get jdk15 >>> installed and running on this specific machine, despite it's age. >>> >>> Cheers, >>> James >>> >> >> AFAICT yes, it is possible that 1Gb (try 2Gb to be sure) swap >> will solve it. I can start trying to imagine how long it would take >> to compile jdk15, though. And even if you do succeed, an >> average java application can take about 100Mb of RAM >> right from the start. So you should really choose between a >> newer box and a sensible programming language. > > Thanks for the tip. I upped the additional swapfile size to 2GB and > tried again, with the same results. > > Granted I understand that expecting so much from this little machine > is really pushing it, it will eventually just be running a small > java-based server, that unfortunately requires jdk15. I wouldn't ever > choose it on purpose. > > With a total swap size of roughly 2.5GB still generating failures, is > this a lost cause, or should I be looking for additional solutions? Hmm. I successfully compiled jdk15 with 256 MB RAM and 1 GB swap on an i386 machine. I suspect some other problem with your system. I can offer no speculation to the nature of your problem though. Greets, Helge ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: jdk15 on 6.0
On Apr 2, 2006, at 11:41 AM, Andrew Pantyukhin wrote: On 4/2/06, james g. <[EMAIL PROTECTED]> wrote: FreeBSD Land: I've seen this question asked on this very list, and once or twice on the web, but have yet to find a solution. I'm attempting to compile jdk15 on an older machine, and at first attempted it on a 4.11 install. The failures there encouraged me to finally upgrade the machine to 6.0. So now, I have a fully patched, fresh 6.0 installation. The machine has 128MB physical ram, and I doubled the default swap space. When I continued to run into memory errors while attempting to compile the jdk, I added an additional swap file of 512MB. Even with all this additional swap space, I'm getting the following compilation error every time: `/usr/ports/java/jdk15/work/control/build/bsd-i586/hotspot-i586/tmp/ bsd_i486_compiler2/jvmg' gmake[3]: Entering directory `/usr/ports/java/jdk15/work/control/ build/bsd-i586/hotspot-i586/tmp/bsd_i486_compiler2/jvmg' Compiling ../generated/adfiles/ad_i486.cpp virtual memory exhausted: Cannot allocate memory gmake[3]: *** [ad_i486.o] Error 1 gmake[3]: Leaving directory `/usr/ports/java/jdk15/work/control/ build/ bsd-i586/hotspot-i586/tmp/bsd_i486_compiler2/jvmg' gmake[2]: *** [the_vm] Error 2 gmake[2]: Leaving directory `/usr/ports/java/jdk15/work/control/ build/ bsd-i586/hotspot-i586/tmp/bsd_i486_compiler2/jvmg' gmake[1]: *** [jvmg] Error 2 gmake[1]: Leaving directory `/usr/ports/java/jdk15/work/control/ build/ bsd-i586/hotspot-i586/tmp' gmake: *** [jvmg] Error 2 *** Error code 2 Stop in /usr/ports/java/jdk15. Does jdk15 really require more swapspace? I don't making the additional swap file larger, but pushing 1GB of swap already is leading me to believe there is another cause. Any help is greatly appreciated, as I'd really like to get jdk15 installed and running on this specific machine, despite it's age. Cheers, James AFAICT yes, it is possible that 1Gb (try 2Gb to be sure) swap will solve it. I can start trying to imagine how long it would take to compile jdk15, though. And even if you do succeed, an average java application can take about 100Mb of RAM right from the start. So you should really choose between a newer box and a sensible programming language. Thanks for the tip. I upped the additional swapfile size to 2GB and tried again, with the same results. Granted I understand that expecting so much from this little machine is really pushing it, it will eventually just be running a small java- based server, that unfortunately requires jdk15. I wouldn't ever choose it on purpose. With a total swap size of roughly 2.5GB still generating failures, is this a lost cause, or should I be looking for additional solutions? Cheers, James ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: jdk15 on 6.0
On 4/2/06, james g. <[EMAIL PROTECTED]> wrote: > FreeBSD Land: > > I've seen this question asked on this very list, and once or twice on > the web, but have yet to find a solution. > > I'm attempting to compile jdk15 on an older machine, and at first > attempted it on a 4.11 install. The failures there encouraged me to > finally upgrade the machine to 6.0. > > So now, I have a fully patched, fresh 6.0 installation. The machine > has 128MB physical ram, and I doubled the default swap space. When I > continued to run into memory errors while attempting to compile the > jdk, I added an additional swap file of 512MB. Even with all this > additional swap space, I'm getting the following compilation error > every time: > > `/usr/ports/java/jdk15/work/control/build/bsd-i586/hotspot-i586/tmp/ > bsd_i486_compiler2/jvmg' > gmake[3]: Entering directory `/usr/ports/java/jdk15/work/control/ > build/bsd-i586/hotspot-i586/tmp/bsd_i486_compiler2/jvmg' > Compiling ../generated/adfiles/ad_i486.cpp > virtual memory exhausted: Cannot allocate memory > gmake[3]: *** [ad_i486.o] Error 1 > gmake[3]: Leaving directory `/usr/ports/java/jdk15/work/control/build/ > bsd-i586/hotspot-i586/tmp/bsd_i486_compiler2/jvmg' > gmake[2]: *** [the_vm] Error 2 > gmake[2]: Leaving directory `/usr/ports/java/jdk15/work/control/build/ > bsd-i586/hotspot-i586/tmp/bsd_i486_compiler2/jvmg' > gmake[1]: *** [jvmg] Error 2 > gmake[1]: Leaving directory `/usr/ports/java/jdk15/work/control/build/ > bsd-i586/hotspot-i586/tmp' > gmake: *** [jvmg] Error 2 > *** Error code 2 > > Stop in /usr/ports/java/jdk15. > > > Does jdk15 really require more swapspace? I don't making the > additional swap file larger, but pushing 1GB of swap already is > leading me to believe there is another cause. > > Any help is greatly appreciated, as I'd really like to get jdk15 > installed and running on this specific machine, despite it's age. > > Cheers, > James > > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" > AFAICT yes, it is possible that 1Gb (try 2Gb to be sure) swap will solve it. I can start trying to imagine how long it would take to compile jdk15, though. And even if you do succeed, an average java application can take about 100Mb of RAM right from the start. So you should really choose between a newer box and a sensible programming language. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
