Bug#467486: Investigations about failure

2008-04-10 Thread Andreas Kirschbaum
gcc-4.2 and gcc-4.3 differ in the representation of char values: gcc-4.2
represents a char as a 32 bit value (bits 0..7 is the char value; bits
8..31 are always set to zero); gcc-4.3 uses only the lower 8 bits,
ignoring bits 8..31.

kaffe defines typedef unsigned char jboolean; in
kaffe-1.1.8/libraries/javalib/external/classpath/include/jni_md-x86-linux-gnu.h
but assumes %eax is 0/1 in compiled Java code. This makes compiled Java
code calling into native C code almost always assume true for jboolean
return values due to the non-zero garbage in bits 8..31.


Compiling the following source demonstrates the issue: compiled with
gcc-4.2, the return value in %eax always is either 0 or 1. Compiled with
gcc-4.3, only %al is set ot 0 or 1; the remaining bits 8..31 of %eax
remain unset.

~ cat t.c
unsigned char f(int x)
{
return x == 3;
}

~ gcc-4.2 -O3 -c -s t.c  objdump -d t.o

t.o: file format elf32-i386

Disassembly of section .text:

 f:
   0:   55  push   %ebp
   1:   31 c0   xor%eax,%eax
   3:   89 e5   mov%esp,%ebp
   5:   83 7d 08 03 cmpl   $0x3,0x8(%ebp)
   9:   5d  pop%ebp
   a:   0f 94 c0sete   %al
   d:   c3  ret

~ gcc-4.3 -O3 -c -s t.c  objdump -d t.o

t.o: file format elf32-i386

Disassembly of section .text:

 f:
   0:   55  push   %ebp
   1:   89 e5   mov%esp,%ebp
   3:   83 7d 08 03 cmpl   $0x3,0x8(%ebp)
   7:   5d  pop%ebp
   8:   0f 94 c0sete   %al
   b:   c3  ret



___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers


Bug#459281: Cannot reproduce the issue

2008-04-06 Thread Andreas Kirschbaum
I cannot reproduce this issue: all of jdk1.5.0_02, cacao, kaffe, and gij
produce charts on both AMD x32 and x64 machines.

The only remaining issues are:

- The charts produced by caco/kaffe/gij are about twice as large as the
  charts produced by jdk1.5.0_02.

- The chart produced by kaffe has one pixel cut off from both the domain
  axis label and the label below it.

The attached archive contains the produced charts. The exact same output
files are produced on both x32 and x64 machines. The files cpuinfo-*.txt
show the output of /proc/cpuinfo.

ii  cacao0.98-2   Java 
virtual machine
ii  gij  4:4.3-1  The GNU 
Java bytecode interpreter
ii  kaffe2:1.1.8-3A JVM to 
run Java bytecode
ii  libjcommon-java  1.0.10.dfsg-1General 
Purpose library for Java
ii  libjfreechart-java   1.0.9-1  Chart 
library for Java


test-charts.tar.gz
Description: Binary data
___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers

Bug#470330: Patch to fix build failure

2008-04-06 Thread Andreas Kirschbaum
tags 470330 + patch
thanks
Linux kernel 2.6.25 removed sequencer instrument layer support: see
http://kerneltrap.org/mailarchive/git-commits-head/2008/1/31/669604

libasound2 removed this support in version 1.0.16 (1.0.15rc3 still
supports it).

The removed events are SND_SEQ_EVENT_SAMPLE* and
SND_SEQ_EVENT_INSTR_BEGIN* in libasound2's changeset 2343:e7678910554f.

The attached patch removes access to the now non-existing symbols from
libtritonus-java. It solves the build failure.

The attached patch removed-code.diff should be added as
libtritonus-java-20070428/debian/patches/removed-code.diff and applied
last in libtritonus-java-20070428/debian/patches/series.
diff -urd libtritonus-java-20070428.orig/src/lib/alsa/constants_check.h libtritonus-java-20070428/src/lib/alsa/constants_check.h
--- libtritonus-java-20070428.orig/src/lib/alsa/constants_check.h	2002-08-03 07:56:35.0 +0200
+++ libtritonus-java-20070428/src/lib/alsa/constants_check.h	2008-04-06 15:29:08.0 +0200
@@ -70,6 +70,7 @@
 	assert(SND_SEQ_EVENT_PORT_CHANGE == org_tritonus_lowlevel_alsa_AlsaSeq_SND_SEQ_EVENT_PORT_CHANGE);
 	assert(SND_SEQ_EVENT_PORT_SUBSCRIBED == org_tritonus_lowlevel_alsa_AlsaSeq_SND_SEQ_EVENT_PORT_SUBSCRIBED);
 	assert(SND_SEQ_EVENT_PORT_UNSUBSCRIBED == org_tritonus_lowlevel_alsa_AlsaSeq_SND_SEQ_EVENT_PORT_UNSUBSCRIBED);
+/* removed since libasound2 1.0.16
 	assert(SND_SEQ_EVENT_SAMPLE == org_tritonus_lowlevel_alsa_AlsaSeq_SND_SEQ_EVENT_SAMPLE);
 	assert(SND_SEQ_EVENT_SAMPLE_CLUSTER == org_tritonus_lowlevel_alsa_AlsaSeq_SND_SEQ_EVENT_SAMPLE_CLUSTER);
 	assert(SND_SEQ_EVENT_SAMPLE_START == org_tritonus_lowlevel_alsa_AlsaSeq_SND_SEQ_EVENT_SAMPLE_START);
@@ -79,6 +80,7 @@
 	assert(SND_SEQ_EVENT_SAMPLE_LOOP == org_tritonus_lowlevel_alsa_AlsaSeq_SND_SEQ_EVENT_SAMPLE_LOOP);
 	assert(SND_SEQ_EVENT_SAMPLE_POSITION == org_tritonus_lowlevel_alsa_AlsaSeq_SND_SEQ_EVENT_SAMPLE_POSITION);
 	assert(SND_SEQ_EVENT_SAMPLE_PRIVATE1 == org_tritonus_lowlevel_alsa_AlsaSeq_SND_SEQ_EVENT_SAMPLE_PRIVATE1);
+*/
 	assert(SND_SEQ_EVENT_USR0 == org_tritonus_lowlevel_alsa_AlsaSeq_SND_SEQ_EVENT_USR0);
 	assert(SND_SEQ_EVENT_USR1 == org_tritonus_lowlevel_alsa_AlsaSeq_SND_SEQ_EVENT_USR1);
 	assert(SND_SEQ_EVENT_USR2 == org_tritonus_lowlevel_alsa_AlsaSeq_SND_SEQ_EVENT_USR2);
@@ -89,6 +91,7 @@
 	assert(SND_SEQ_EVENT_USR7 == org_tritonus_lowlevel_alsa_AlsaSeq_SND_SEQ_EVENT_USR7);
 	assert(SND_SEQ_EVENT_USR8 == org_tritonus_lowlevel_alsa_AlsaSeq_SND_SEQ_EVENT_USR8);
 	assert(SND_SEQ_EVENT_USR9 == org_tritonus_lowlevel_alsa_AlsaSeq_SND_SEQ_EVENT_USR9);
+/* removed since libasound2 1.0.16
 	assert(SND_SEQ_EVENT_INSTR_BEGIN == org_tritonus_lowlevel_alsa_AlsaSeq_SND_SEQ_EVENT_INSTR_BEGIN);
 	assert(SND_SEQ_EVENT_INSTR_END == org_tritonus_lowlevel_alsa_AlsaSeq_SND_SEQ_EVENT_INSTR_END);
 	assert(SND_SEQ_EVENT_INSTR_INFO == org_tritonus_lowlevel_alsa_AlsaSeq_SND_SEQ_EVENT_INSTR_INFO);
@@ -108,6 +111,7 @@
 	assert(SND_SEQ_EVENT_INSTR_CLUSTER_GET == org_tritonus_lowlevel_alsa_AlsaSeq_SND_SEQ_EVENT_INSTR_CLUSTER_GET);
 	assert(SND_SEQ_EVENT_INSTR_CLUSTER_RESULT == org_tritonus_lowlevel_alsa_AlsaSeq_SND_SEQ_EVENT_INSTR_CLUSTER_RESULT);
 	assert(SND_SEQ_EVENT_INSTR_CHANGE == org_tritonus_lowlevel_alsa_AlsaSeq_SND_SEQ_EVENT_INSTR_CHANGE);
+*/
 	assert(SND_SEQ_EVENT_SYSEX == org_tritonus_lowlevel_alsa_AlsaSeq_SND_SEQ_EVENT_SYSEX);
 	assert(SND_SEQ_EVENT_BOUNCE == org_tritonus_lowlevel_alsa_AlsaSeq_SND_SEQ_EVENT_BOUNCE);
 	assert(SND_SEQ_EVENT_USR_VAR0 == org_tritonus_lowlevel_alsa_AlsaSeq_SND_SEQ_EVENT_USR_VAR0);
___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers

Bug#439614: Investigations about/suggested fix for build failure

2008-04-06 Thread Andreas Kirschbaum
The build failure is because the function matrix-concat() was removed
from libjaxen-java (which is used by this package);
http://jaxen.org/status.html contains

Jaxen 1.1 Beta 12
[...]
The matrix-concat extension function has been removed because its
license staus was unclear, the originator could not be contacted,
and it was undocumented and untested. If someone cares to
reimplement it, it could be restored in the future.


Removing the unit test file
dom4j-1.6.1+dfsg/src/test/org/dom4j/xpath/MatrixConcatTest.java fixes
the build failure.



___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers


Bug#439614: Investigations about/suggested fix for build failure

2008-04-06 Thread Andreas Kirschbaum
A simple grep for matrix-concat, matrix, and concat didn't show up
anything other than this unit test and
dom4j-1.6.1+dfsg/docs/status.html. Can't give any other information
since I don't know the internals of this package.



___
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers