libffi2-dev: wrong libdir in /usr/lib/libffi.la

[Debian Bug Importer]

Automatically imported from Debian bug report #256978 http://bugs.debian.org/256978

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 30 Jun 2004 10:06:24 +0100
From: Ross Burton <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: Lost dependencies on libgmp3 and libffi2

Package: kaffe-pthreads
Version: 2:1.1.4.PRE1.1.5-6
Severity: grave

This version of kaffe-pthreads has lost the dependency on libgmp3 and libffi2,
so kaffe won't start.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.4.26-1-686
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8

Versions of packages kaffe-pthreads depends on:
ii kaffe-common 2:1.1.4.PRE1.1.5-6 Files shared between all Kaffe VM
ii libc6 2.3.2.ds1-13 GNU C Library: Shared libraries an
ii libice6 4.3.0.dfsg.1-5 Inter-Client Exchange library
ii libsm6 4.3.0.dfsg.1-5 X Window System Session Management
ii libx11-6 4.3.0.dfsg.1-5 X Window System protocol client li
ii libxext6 4.3.0.dfsg.1-5 X Window System miscellaneous exte
ii xlibs 4.3.0.dfsg.1-5 X Window System client libraries m

-- no debconf information

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 30 Jun 2004 16:27:29 +0200
From: Arnaud Vandyck <email address hidden>
To: <email address hidden>, <email address hidden>
Cc: <email address hidden>
cc: Arnaud Vandyck <email address hidden>
Subject: libffi2-dev: wrong libdir in /usr/lib/libffi.la

--=-=-=

reassign 253059 gcc-3.3
retitle 253059 libffi2-dev: wrong libdir in /usr/lib/libffi.la
retitle 256978 libffi2-dev: wrong libdir in /usr/lib/libffi.la
thanks

arnaud@oz:~$ sudo apt-get install -f libffi2-dev=1:3.3.4-1
...
arnaud@oz:~$ cat /usr/lib/libffi.la | grep usr/lib
libdir='/usr/lib'
arnaud@oz:~$ sudo apt-get install -f libffi2-dev=1:3.3.4-2
..
arnaud@oz:~$ cat /usr/lib/libffi.la | grep usr/lib
libdir='/usr/lib/.'

Because of this, my package can not link to the correct libs. Thanks to
fix it ;-)

Cheers,

--
Arnaud Vandyck

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBA4s3T4vzFZu62tMIRAkVeAKCMquxo7j5/PePNcfF9r3E+oiLJuACeKH4J
BNGNq51r0Qge8g9iCbtY8mc=
=QhAf
-----END PGP SIGNATURE-----
--=-=-=--

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 30 Jun 2004 16:41:04 +0200
From: Arnaud Vandyck <email address hidden>
To: <email address hidden>
Subject: libffi2-dev: wrong libdir in /usr/lib/libffi.la

--=-=-=

reassign 256978 gcc-3.3
merge 256978 253059
thanks

--
Arnaud Vandyck

< jaybonci> actually d-i stands for "divine intervention" ;)
  -- in #debian-devel

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBA4tED4vzFZu62tMIRAtTRAKCe1FblsppMTryE0+BJy4obDpJyFQCfdnSp
ZKtPVSfb6+N9gA91nL1E0kA=
=Z0eo
-----END PGP SIGNATURE-----
--=-=-=--

[Matt Zimmerman (mdz)]

This bug has been marked as a duplicate of bug 6908.

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Fri, 2 Jul 2004 07:22:49 +0200
From: Matthias Klose <email address hidden>
To: <email address hidden>
Cc: Arnaud Vandyck <email address hidden>,
 Debian GCC maintainers <email address hidden>(gcc-3.3 #253059 #256978),
 <email address hidden> (Ean R. Schuessler) (kaffe-pthreads #256978)
Subject: Re: Processed: libffi2-dev: wrong libdir in /usr/lib/libffi.la

clone 253059 -1
unmerge -1
severity -1 important
retitle -1 libffi2-dev: non canonical path in /usr/lib/libffi.la
unmerge 253059
reassign 253059 libgtk2-java
reassign 256978 kaffe-pthreads
thanks

the path is correct. any idea, why these two packages don't get the
dependency.

Debian Bug Tracking System writes:
> Processing commands for <email address hidden>:
>
> > reassign 256978 gcc-3.3
> Bug#256978: libffi2-dev: wrong libdir in /usr/lib/libffi.la
> Bug reassigned from package `kaffe-pthreads' to `gcc-3.3'.
>
> > merge 256978 253059
> Bug#253059: libffi2-dev: wrong libdir in /usr/lib/libffi.la
> Bug#256978: libffi2-dev: wrong libdir in /usr/lib/libffi.la
> Merged 253059 256978.
>
> > thanks
> Stopping processing here.
>
> Please contact me if you need assistance.
>
> Debian bug tracking system administrator
> (administrator, Debian Bugs database)
>
>
> --
> To UNSUBSCRIBE, email to <email address hidden>
> with a subject of "unsubscribe". Trouble? Contact <email address hidden>

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Fri, 2 Jul 2004 07:38:48 +0200
From: Matthias Klose <email address hidden>
To: <email address hidden>
Subject: Re: Processed: Re: Processed: libffi2-dev: wrong libdir in /usr/lib/libffi.la

clone 253059 -1
unmerge -1
severity -1 important
reassign -1 libffi2-dev
retitle -1 libffi2-dev: non canonical path in /usr/lib/libffi.la
retitle 253059 libgtk2-java depends on libgtk2-jni, which is not available
retitle 256978 Lost dependencies on libgmp3 and libffi2
thanks

[Debian Bug Importer (debzilla)]

Message-Id: <E1BgIUb-0001Qd-C1@localhost>
Date: Fri, 2 Jul 2004 08:29:15 +0100
From: Mark Howard <email address hidden>
To: Matthias Klose <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: #253059 libffi2-dev: wrong libdir in /usr/lib/libffi.la

Matthias,

When you reassign, merge, change severity of bug reports, please send an
explanatory message. In most cases, this means CC'ing your message to
the bug.

From the BTS, I managed to find your original message which made the
changes. This had the comment:
> the path is correct. any idea, why these two packages don't get the
> dependency.

Could you please explain that further.

The package changed from having libdir='/usr/lib' to having libdir='/usr/lib/.'

Why?
This change has clearly broken other packages, so please consider that
your package may be in error rather than the other packages.

I am no expert in these matters, but libdir='/usr/lib/' seems to make
more sense.

--
  .''`. Mark Howard
 : :' :
 `. `' http://www.tildemh.com
   `- <email address hidden> | <email address hidden>

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sat, 3 Jul 2004 07:03:14 +0200
From: Matthias Klose <email address hidden>
To: Mark Howard <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: Re: #253059 libffi2-dev: wrong libdir in /usr/lib/libffi.la

Mark Howard writes:
> Matthias,
>
> When you reassign, merge, change severity of bug reports, please send an
> explanatory message. In most cases, this means CC'ing your message to
> the bug.

well, I renamed the report.

> >From the BTS, I managed to find your original message which made the
> changes. This had the comment:
> > the path is correct. any idea, why these two packages don't get the
> > dependency.
>
> Could you please explain that further.
>
> The package changed from having libdir='/usr/lib' to having libdir='/usr/lib/.'
>
> Why?
> This change has clearly broken other packages, so please consider that
> your package may be in error rather than the other packages.
>
> I am no expert in these matters, but libdir='/usr/lib/' seems to make
> more sense.

/usr/lib/. and /usr/lib are both valid path names, even if you append
to it. I'll change that with the next upload, but IMO there is no
requirement that path names in these files have to be normalized.

 Matthias

[Debian Bug Importer (debzilla)]

Message-Id: <E1Bhvdv-0001pz-00@dual>
Date: Tue, 06 Jul 2004 21:30:15 +0200
From: Goswin Brederlow <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: kaffe: Problem of the lib path

Package: kaffe
Version: 2:1.1.4.PRE1.1.5-5
Severity: normal
Followup-For: Bug #256978

Hi,

as you said in your last message "/usr/lib/." is a valid library patch
on its own.

The problem arises with libtool checking the lib path against the
system paths to see if rpath will be needed or not. Since "/usr/lib/."
is not one of the standard search path libtool will use rpath for this
library. That on its own is buggy but does not stop the binaries from
working.

But the problem becomes even more serious when dpkg-shlibdeps tries to
calculate shared library dependancies. dpkg-shlibdeps compares the
output from ldd (which includes the rpath /usr/lib/./) with dpkgs file
database to find packages providing the library, which fails because
dpkg has no . in there. Hence the missing Depends.

On amd64 the lib path is even more strange: /usr/lib/../lib64. Since
lib64 is a link to lib that ends up in the right place but again
libtool and dpkgs file database won't work with that path.

MfG
 Goswin

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.5-amd64
Locale: LANG=C, LC_CTYPE=de_DE

Versions of packages kaffe depends on:
ii kaffe-pthreads 2:1.1.4.PRE1.1.5-5 A POSIX threads enabled version of

-- no debconf information

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Tue, 06 Jul 2004 22:27:12 +0200
From: Arnaud Vandyck <email address hidden>
To: Goswin Brederlow <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#256978: kaffe: Problem of the lib path

--=-=-=

Goswin Brederlow <email address hidden> writes:

> as you said in your last message "/usr/lib/." is a valid library patch
> on its own.
>
> The problem arises with libtool checking the lib path against the
> system paths to see if rpath will be needed or not. Since "/usr/lib/."
> is not one of the standard search path libtool will use rpath for this
> library. That on its own is buggy but does not stop the binaries from
> working.
>
> But the problem becomes even more serious when dpkg-shlibdeps tries to
> calculate shared library dependancies. dpkg-shlibdeps compares the
> output from ldd (which includes the rpath /usr/lib/./) with dpkgs file
> database to find packages providing the library, which fails because
> dpkg has no . in there. Hence the missing Depends.
>
> On amd64 the lib path is even more strange: /usr/lib/../lib64. Since
> lib64 is a link to lib that ends up in the right place but again
> libtool and dpkgs file database won't work with that path.

Do you mean a temporary work around could be to hard copy dependencies
and not let them automatically be filled by dpkg-shlibdeps?

Thanks for your help,

Cheers,

--
Arnaud Vandyck

This is Unix we're talking about, remember. It's not supposed to be
nice for the applications programmer.
  -- Matthew Danish on debian-devel

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBA6wsi4vzFZu62tMIRAiQaAJ4ir4ozPZvya9ipRGWJLmuaV1ZU7ACgp4sx
fOrK8IVSfvp9DzccgreCBeg=
=9+8x
-----END PGP SIGNATURE-----
--=-=-=--

[Debian Bug Importer (debzilla)]

Message-ID: <20040706205859.GA10605@Zimmer>
Date: Tue, 6 Jul 2004 15:58:59 -0500
From: Drew Scott Daniels <email address hidden>
To: Goswin Brederlow <email address hidden>,
 <email address hidden>
Subject: dpkg-dev bug? Bug#256978: kaffe: Problem of the lib path

Hi,
Is this an unfiled bug on dpkg-dev and dpkg-cross? Should libtool be
fixed (libtool1.4 may not be fixed, see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=224437&msg=28&att=0)?

     Drew Daniels

On Tue, Jul 06, 2004 at 09:30:15PM +0200, Goswin Brederlow wrote:
> Package: kaffe
> Version: 2:1.1.4.PRE1.1.5-5
> Severity: normal
> Followup-For: Bug #256978
>
> Hi,
>
> as you said in your last message "/usr/lib/." is a valid library patch
> on its own.
>
> The problem arises with libtool checking the lib path against the
> system paths to see if rpath will be needed or not. Since "/usr/lib/."
> is not one of the standard search path libtool will use rpath for this
> library. That on its own is buggy but does not stop the binaries from
> working.
>
> But the problem becomes even more serious when dpkg-shlibdeps tries to
> calculate shared library dependancies. dpkg-shlibdeps compares the
> output from ldd (which includes the rpath /usr/lib/./) with dpkgs file
> database to find packages providing the library, which fails because
> dpkg has no . in there. Hence the missing Depends.
>
> On amd64 the lib path is even more strange: /usr/lib/../lib64. Since
> lib64 is a link to lib that ends up in the right place but again
> libtool and dpkgs file database won't work with that path.
>
> MfG
> Goswin
>
> -- System Information:
> Debian Release: testing/unstable
> APT prefers unstable
> APT policy: (500, 'unstable')
> Architecture: amd64 (x86_64)
> Kernel: Linux 2.6.5-amd64
> Locale: LANG=C, LC_CTYPE=de_DE
>
> Versions of packages kaffe depends on:
> ii kaffe-pthreads 2:1.1.4.PRE1.1.5-5 A POSIX threads enabled version of
>
> -- no debconf information
>
>

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 07 Jul 2004 03:25:39 +0200
From: Goswin von Brederlow <email address hidden>
To: Arnaud Vandyck <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#256978: kaffe: Problem of the lib path

Arnaud Vandyck <email address hidden> writes:

> Goswin Brederlow <email address hidden> writes:
>
>> as you said in your last message "/usr/lib/." is a valid library patch
>> on its own.
>>
>> The problem arises with libtool checking the lib path against the
>> system paths to see if rpath will be needed or not. Since "/usr/lib/."
>> is not one of the standard search path libtool will use rpath for this
>> library. That on its own is buggy but does not stop the binaries from
>> working.
>>
>> But the problem becomes even more serious when dpkg-shlibdeps tries to
>> calculate shared library dependancies. dpkg-shlibdeps compares the
>> output from ldd (which includes the rpath /usr/lib/./) with dpkgs file
>> database to find packages providing the library, which fails because
>> dpkg has no . in there. Hence the missing Depends.
>>
>> On amd64 the lib path is even more strange: /usr/lib/../lib64. Since
>> lib64 is a link to lib that ends up in the right place but again
>> libtool and dpkgs file database won't work with that path.
>
>
> Do you mean a temporary work around could be to hard copy dependencies
> and not let them automatically be filled by dpkg-shlibdeps?
>
> Thanks for your help,
>
> Cheers,

How about a shlibs.local file containing the libfii2-dev package for
the libffi2 lib with the broken rpath? That should fix the problem now
and get ignored when libffi2-dev gets fixed.

Haven't tested that though.

MfG
        Goswin

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Wed, 07 Jul 2004 09:22:43 +0200
From: Goswin von Brederlow <email address hidden>
To: Drew Scott Daniels <email address hidden>
Cc: Goswin Brederlow <email address hidden>,
 <email address hidden>
Subject: Re: dpkg-dev bug? Bug#256978: kaffe: Problem of the lib path

Drew Scott Daniels <email address hidden> writes:

> Hi,
> Is this an unfiled bug on dpkg-dev and dpkg-cross? Should libtool be
> fixed (libtool1.4 may not be fixed, see
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=224437&msg=28&att=0)?
>
> Drew Daniels

I don't think you can fix this. What if a user has usr linked
somewhere else or lib? You can't just canonify the path. You could
check every file in dpkgs database if it ends up in the same spot the
library is found but thats very costly.

It realy is the sources fault for having the wrong path in the .la
file.

> On Tue, Jul 06, 2004 at 09:30:15PM +0200, Goswin Brederlow wrote:
>> Package: kaffe
>> Version: 2:1.1.4.PRE1.1.5-5
>> Severity: normal
>> Followup-For: Bug #256978
>>
>> Hi,
>>
>> as you said in your last message "/usr/lib/." is a valid library patch
>> on its own.
>>
>> The problem arises with libtool checking the lib path against the
>> system paths to see if rpath will be needed or not. Since "/usr/lib/."
>> is not one of the standard search path libtool will use rpath for this
>> library. That on its own is buggy but does not stop the binaries from
>> working.
>>
>> But the problem becomes even more serious when dpkg-shlibdeps tries to
>> calculate shared library dependancies. dpkg-shlibdeps compares the
>> output from ldd (which includes the rpath /usr/lib/./) with dpkgs file
>> database to find packages providing the library, which fails because
>> dpkg has no . in there. Hence the missing Depends.
>>
>> On amd64 the lib path is even more strange: /usr/lib/../lib64. Since
>> lib64 is a link to lib that ends up in the right place but again
>> libtool and dpkgs file database won't work with that path.
>>
>> MfG
>> Goswin
>>
>> -- System Information:
>> Debian Release: testing/unstable
>> APT prefers unstable
>> APT policy: (500, 'unstable')
>> Architecture: amd64 (x86_64)
>> Kernel: Linux 2.6.5-amd64
>> Locale: LANG=C, LC_CTYPE=de_DE
>>
>> Versions of packages kaffe depends on:
>> ii kaffe-pthreads 2:1.1.4.PRE1.1.5-5 A POSIX threads enabled version of
>>
>> -- no debconf information
>>
>>

MfG
        Goswin

[Debian Bug Importer (debzilla)]

Message-ID: <email address hidden>
Date: Sat, 10 Jul 2004 16:56:39 +0200
From: Arnaud Vandyck <email address hidden>
To: Drew Scott Daniels <email address hidden>
Cc: <email address hidden>, <email address hidden>, Ean Schuessler
 <email address hidden>, <email address hidden>, Dalibor Topic <email address hidden>
Subject: Re: Bug#258448: kaffe_2:1.1.4.PRE1.1.5-7(hppa/unstable): FTBFS: bad
 build-depends

--=-=-=
Content-Transfer-Encoding: quoted-printable

severity 258448 grave
severity 258208 grave
severity 257173 grave
severity 257152 grave
tags 256978 + pending
tags 258448 + pending
tags 258208 + pending
merge 256978 258448 258208 257173 257152
thanks

Drew Scott Daniels <email address hidden> writes:

> Hi,
> See bug 257066 "FTBFS: libffi2-dev 1:3.3.4-1 missing (archive has
> 1:3.3.4-2)" and 257173 "kaffe: Wrong build dependency on libffi2-dev.".
>
> A workaround for (gcc) 257240 resulted in (kaffe) 257066 & 257173 which
> caused (java-gnome) 253059.
>
> I'd recommend merging the kaffe bugs so they can all be closed at once
> unless there's more than one solution. If non-canonical directory names
> are to be accepted then a bug should remain open until that's resolved.

Hi Drew, Hi all,

I'm chatting with kaffe upstream and I'll upload the latest CVS HEAD
From=20kaffe when they'll finish to fix some issues. I can tell that the
problem you refer is not because of kaffe but was because of libffi (and
it's now fixed).

Thanks for your time, patience and help,

Cheers,

=2D-=20
Arnaud Vandyck

< asuffield> a workstation is anything you can stick on somebodies desk
             and con them into using
  -- in #debian-devel

--=-=-=
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBA8AOq4vzFZu62tMIRAlKxAJkBSJTYFPmsa/CubIWJER05Vf72WwCglTDJ
jHJy7Z+FeS3Xu0tBqtFWAi8=
=ZT2J
-----END PGP SIGNATURE-----
--=-=-=--

[Debian Bug Importer (debzilla)]

Message-Id: <email address hidden>
Date: Sat, 10 Jul 2004 21:47:08 -0400
From: Arnaud Vandyck <email address hidden>
To: <email address hidden>
Subject: Bug#256978: fixed in kaffe 2:1.1.4.PRE1.1.5-8

Source: kaffe
Source-Version: 2:1.1.4.PRE1.1.5-8

We believe that the bug you reported is fixed in the latest version of
kaffe, which is due to be installed in the Debian FTP archive:

jikes-kaffe_1.1.4.PRE1.1.5-8_all.deb
  to pool/main/k/kaffe/jikes-kaffe_1.1.4.PRE1.1.5-8_all.deb
kaffe-common_1.1.4.PRE1.1.5-8_all.deb
  to pool/main/k/kaffe/kaffe-common_1.1.4.PRE1.1.5-8_all.deb
kaffe-dev_1.1.4.PRE1.1.5-8_all.deb
  to pool/main/k/kaffe/kaffe-dev_1.1.4.PRE1.1.5-8_all.deb
kaffe-doc_1.1.4.PRE1.1.5-8_all.deb
  to pool/main/k/kaffe/kaffe-doc_1.1.4.PRE1.1.5-8_all.deb
kaffe-jthreads_1.1.4.PRE1.1.5-8_powerpc.deb
  to pool/main/k/kaffe/kaffe-jthreads_1.1.4.PRE1.1.5-8_powerpc.deb
kaffe-pthreads_1.1.4.PRE1.1.5-8_powerpc.deb
  to pool/main/k/kaffe/kaffe-pthreads_1.1.4.PRE1.1.5-8_powerpc.deb
kaffe_1.1.4.PRE1.1.5-8.diff.gz
  to pool/main/k/kaffe/kaffe_1.1.4.PRE1.1.5-8.diff.gz
kaffe_1.1.4.PRE1.1.5-8.dsc
  to pool/main/k/kaffe/kaffe_1.1.4.PRE1.1.5-8.dsc
kaffe_1.1.4.PRE1.1.5-8_all.deb
  to pool/main/k/kaffe/kaffe_1.1.4.PRE1.1.5-8_all.deb
kjc_1.1.4.PRE1.1.5-8_all.deb
  to pool/main/k/kaffe/kjc_1.1.4.PRE1.1.5-8_all.deb

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to <email address hidden>,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Arnaud Vandyck <email address hidden> (supplier of updated kaffe package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing <email address hidden>)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sat, 10 Jul 2004 18:03:10 +0200
Source: kaffe
Binary: kaffe-dev kaffe-common jikes-kaffe kaffe-pthreads-profile kaffe-pthreads kaffe-doc kaffe kjc kaffe-jthreads
Architecture: source all powerpc
Version: 2:1.1.4.PRE1.1.5-8
Distribution: unstable
Urgency: low
Maintainer: Ean R. Schuessler <email address hidden>
Changed-By: Arnaud Vandyck <email address hidden>
Description:
 jikes-kaffe - Wrapper for jikes using Kaffe classes
 kaffe - A JVM to run Java bytecode
 kaffe-common - Files shared between all Kaffe VM versions
 kaffe-dev - Header files and other resources for building against Kaffe
 kaffe-doc - Documentation for the Kaffe VM
 kaffe-jthreads - A green threads compile of the Kaffe VM
 kaffe-pthreads - A POSIX threads enabled version of the Kaffe VM
 kjc - A compiler for the Java language written in Java
Closes: 169229 245155 255510 256978 257066 257152 257173 258208 258448
Changes:
 kaffe (2:1.1.4.PRE1.1.5-8) unstable; urgency=low
 .
   * rebuild against new libffi and removed the 'not mipsel' libffi
     condition (libffi should work on mipsel). (Closes: #256978, #257066,
     #257152, #257173, #258208, #258448)
   * added manpages for all the scripts. (Closes: #169229, #245155)
   * co...