probably best to keep this on list... On Tuesday 09 January 2007 08:37, bofh wrote: > On 1/9/07, J.C. Roberts <[EMAIL PROTECTED]> wrote: > > I've been in no rush to build and install java, and in fact I've > > been dreading the idea for a couple months but since you're hitting > > problems, I decided to start on it after reading your post to see > > if I could help. > > Thanx! >
Sorry if my earlier reply seemed a bit pissy but mixing versions OS/pacakage/ports versions is a recurring problem. Obviously stuff changes from OS version to OS version so the odds of version mixing ever working are very slim. Though I now understand you just wanted to give it a try regardless if it was supported (or smart), neither you nor I have any clue what, if any, damage has been done to your package system (tracking and such) by adding a 3.9 package to a 4.0 system. You might also want to note that the heap allocation error you got while building 1.5 is the nearly the same error which you got when trying to run the 3.0 java package on the 4.0 system... If your failing 1.5 build on 4.0 is trying to use the 3.9 package you installed, you're looking at a real mess. > > In the handful of hours since my last reply, I've managed to > > download, build and install jdk 1.3 from ports and I've got 1.4 > > currently building while I type this. As you probably know, having > > a working JVM is a prerequisite for building 1.4 and 1.5. As soon > > as I get 1.4 built and installed, I'll start on 1.5 > > When I built 1.5 on openbsd 3.9-current, it didn't require building > 1.3 and 1.4. It didn't look like 4.0 needed it either. In fact, on > amd64, it won't build jdk1.4 > Though people joke about the chicken-egg problem, you need a working JVM to build the jdk, so maybe you just didn't notice the use/install of a previous version (i.e. scrolled far off screen). If you look at the -CURRENT source tree or read ports@, you'll see things have changed since 4.0 release. Instead of needing to walk backwards from 1.5 to 1.4 to ... they are now using a different jvm to complete the 1.5 build. > > Like OpenOffice, building java seems to use a a lot of swap. How > > large is your swap partition/slice? > > From top: > Memory: Real: 9356K/405M act/tot Free: 2585M Swap: 0K/2000M > used/tot > > From dmesg: > real mem = 3219894272 (3144428K) > avail mem = 2757484544 (2692856K) > using 22937 buffers containing 322195456 bytes (314644K) of memory > > so I should have plenty of ram for it to play with. > not ram, instead your swap disk partition. I'm running 3 GiByte (overkill) for swap simply because this workstation has more disk space than I'll ever need and some day I'd like to build Open Office which supposedly takes up to 2GiBytes of swap space. > > My limits are (far) more conservative than yours: > > > > $ ulimit -a > > time(cpu-seconds) unlimited > > file(blocks) unlimited > > coredump(blocks) unlimited > > data(kbytes) 524288 > > stack(kbytes) 4096 > > lockedmem(kbytes) 315906 > > memory(kbytes) 946192 > > nofiles(descriptors) 64 > > processes 64 > > $ > > > > Lastly, as what user are you building the port? > > root. > > This is basically a brand new install of 4.0 on a amd64 box, and the > following commands: > > % sudo ksh > # cd /usr/ports/devel/jdk/1.5 > # make install > [get error, cuss, read Makefile, make ulimit adjustments, and] > # make install > > Thanx! > Good. > Apropos of nothing - I found that openbsd 4.0 x86 will not install on > this box, the megaraid drivers didn't load properly. Amd64 version > of 4.0 loaded up fine however. You should probably research and report this bug. Kind Regards, JCR
