Riku Voipio schrieb:
> Also I notice the packages are built with ecj using the slowish gij
> interpreter. perhaps the package build could be made faster by using
> gcj precompiled ecj-gcj package?
unfortunately this doesn't help; java-gcj-compat-dev already depends on ecj-gcj.
--
To UNSUBSCRIBE
On Sun, Oct 19, 2008 at 07:50:42PM +0200, Florian Weimer wrote:
> Build times are generally acceptable, with the exception of armel,
> which needed almost 45 hours.
> armel is at about 19 hours, so almost acceptable. However, in
> practice, this likely adds to the 45 hours of openjdk-6, resulting
On Sun, Oct 26, 2008 at 04:53:24PM +0100, Matthias Klose wrote:
> > The s390 failure may be due to too little RAM allocated to the instance
> > (on lxdebian.bfinv.de).
> tried to work around this prentending to have at least some amount of RAM
> (packages in
> experimental); the buildds may swap,
[sorry for not replying earler. please CC the package maintainer address, I
don't read debian-java
on a daily basis]
Florian Weimer schrieb:
> Here are the results of building some OpenJDK packages on the security
> buildd infrastructure (with the test suites disabled).
thanks for doing this.
>
/usr/include/sys/user.h:27:22: error: asm/page.h: No such file or directory
In file included from
../../../src/solaris/native/com/sun/management/UnixOperatingSystem_md.c:52:
/usr/include/sys/procfs.h:32:21: error: asm/elf.h: No such file or directory
Theese look like the result of an outdated l
Here are the results of building some OpenJDK packages on the security
buildd infrastructure (with the test suites disabled).
First, for openjdk-6 6b11-6+lenny1, we have:
Successes: amd64, armel, i386, ia64, mips, mipsel, powerpc, sparc
Failures: alpha, s390
The s390 failure may be due to too li
6 matches
Mail list logo