[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: OpenJDK-7 on kFreeBSD (feedback)



Hi Damien.

On 02/20/2012 08:41 PM, Damien Raude-Morvan wrote:
On Mon, 20 Feb 2012 20:17:26 +0200, Georgi Naplatanov<gosho@oles.biz>
wrote:
Hi.

Hi Georgi!
Nice to see someone interrested by openjdk-7 on kfreebsd :)

I compiled source package openjdk-7-7~b147-2.0 on Wheezy AMD64 without
modification and installed openjdk-7-jre-lib and openjdk-7-jre-headless.

I could not install  :

openjdk-7-jre_7~b147-2.0-1_kfreebsd-amd64.deb
and
openjdk-7-jdk_7~b147-2.0-1_kfreebsd-amd64.deb

because of dependency problems for openjdk-7-jre :

libaccess-bridge-java-jni (>= 1.26.2-6)

We need openjdk-7-jre_*_kfreebsd-amd64 in main archive to build
java-access-bridge for kfreebsd.
So, for now, you can grab libaccess-bridge-java-jni (+ source) on my
people.debian.org page :
http://people.debian.org/~drazzib/openjdk/kfreebsd-snapshots/

Apache Tomcat 6.0.35 (from apache.org) seems to work without problems.

Yep!

I saw the log for kFreeBSD-AMD64 at
https://buildd.debian.org/status/package.php?p=openjdk-7&suite=sid

and it looks strange to me. The error is java.lang.OutOfMemoryError and
the process didn't set "-Xmx512m" parameter to java. Maybe that is the
problem. During the compilation on my machine the parameters -Xmx and
-Xms was always set when java was started. There were and other
parameters also.

I'll have a look at new failures of 7~u3-2.1-1 on kfreebsd. But debian
kfreebsd buildd behavior seems a bit "unstable" to me... :/

I could not reproduce this error on kfreebsd-amd64 neither on kfreebsd-i386 (https://buildd.debian.org/status/package.php?p=openjdk-7&suite=sid)

I used virtual machines with 2 GB RAM and 80 GB disk (with UFS file system) and stable kfreebsd (6.0.4).

My sbuild (0.62.5-1~bpo60+1) configuration is very simple:
~/.sbuildrc
$distribution = 'unstable';
$chroot_mode = 'schroot';

and /etc/schroot/schroot.conf
[sid]
description=Debian sid (unstable)
directory=/chroot/sid
users=rleigh
groups=sbuild
root-groups=root
aliases=unstable,default

Do you think that is good idea to get in touch with system administrators to give information about configuration of these machines so at least this error can be reproducible ?


Cheers,

Best regards
Georgi


Reply to: