Still trying to get my contribution agreement through the process

[Kurt Miller]

On May 6, 2015, at 8:05 PM, "Bryan C. Everly" <bryan at bceassociates.com> wrote:
> 
> Cool.  I'll work on that change tonight.  I'm trying to avoid making OpenBSD its own separate thing like OSX is but I'll figure something out.

Most of the 'bsd' qualified sections apply equally to FreeBSD, OpenBSD and NetBSD. Perhaps as high as 90%. For the exceptions, I would create a sub category for OpenBSD. IIRC, it used to be referred to as OS_VENDOR. Take a look at my diff that adds something like it here:

http://mail.openjdk.java.net/pipermail/bsd-port-dev/attachments/20150427/6eea3d9f/generated-configure.sh.diff

The new variable, VAR_OS_VENDOR lets you call out just the exceptions that are OpenBSD specific, when needed without having to make VAR_OS different for OpenBSD. 

> 
> I did hit an interesting problem in my build of the source.  Looks like Java ran out of heap space.  Is there an option that controls this as part of the build?
> 
> The system is out of resources.
> Consult the following stack trace for details.
> java.lang.OutOfMemoryError: Java heap space
> 	at java.nio.HeapCharBuffer.<init>(HeapCharBuffer.java:57)
> 	at java.nio.CharBuffer.allocate(CharBuffer.java:331)
> 	at com.sun.tools.javac.util.BaseFileManager.decode(BaseFileManager.java:220)

The user you are logged in under needs to be in the login class 'staff',  then you can either edit the staff class datasize default value in /etc/login.conf or change your datasize limit using 'ulimit -d' each time you login, before you build.  

Regards,
-Kurt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/bsd-port-dev/attachments/20150507/3c2763c9/attachment.html>