[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: lang/sun-jdk15 on amd64
any idea why the same procedure wouldn't work with the native 32-bit JDK
running on the target amd64 host itself, using COMPAT_NETBSD32? I'm trying
to do that (I built the native JDK on NetBSD/i386 and installed it on my
NetBSD/amd64 host), but running the 32-bit java binary gives the following:
28531 1 java netbsd32_mmap(0, 0x43e00000, 0, 0x1042,
0xffffffffffffffff, 0, 0, 0) Err#12 ENOMEM
Error occurred during initialization of VM
Could not reserve enough space for object heap
Could not create the Java virtual machine.
I bumped datasize and stacksize limits to very high values but no luck.
On Wed, Jan 14, 2009 at 01:44:57AM +0100, Havard Eidnes wrote:
> [[ re-posted with the correct MIME body type for the attachment
> -- sorry! ]]
> > >> No idea, sorry. I always use the native build, because if I
> > >> run into problems, they can be fixed by the Java porting
> > >> team. The linux package is not open to such fixes.
> > >
> > > How do you manage to build native jdk? It depends on linux
> > > emulated jdk package (which core dumps for me).
> > Hum. You ran into the bootstrap problem. Blech, I remember that one
> > from way back when I hacked at the DEC Alpha port a little.
> > Technically, building the JDK depends on any working JVM, not the
> > linux one per se.
> > There are two paths for you to take; find a working JVM for your box
> > and edit the port dependency so that it uses that JVM, or do the
> > bootstrap on another machine.
> Actually, only a few java commands are needed to be run by
> another java instance during the build. The attached documents
> how I went about getting a native jdk15 running for amd64.
> It can be done, but it's a little quirky to set up.
> - HÃvard
Main Index |
Thread Index |