From: christophe.roux at acoeur.fr (Christophe Roux)
Date: Sat, 20 Jan 2007 15:17:33 +0000 (UTC)
Subject: [Pljava-dev]
	=?utf-8?q?Bug=23390661=3A_pljava_on_Debian_AMD64=3A_?=
	=?utf-8?q?undefined_symbol=3A_JNI=5FCreateJavaVM_during_installati?=
	=?utf-8?q?on?=
References: <1159772249.5314.30.camel@panoramix>
	<4520BCEA.3060304@logix-tt.com>	<1159773977.5314.32.camel@panoramix>
	<4520C346.4050102@logix-tt.com>	<1159775974.5314.40.camel@panoramix>
	<4520CC67.8080606@logix-tt.com>	<1159790884.5314.47.camel@panoramix>
	<4521114A.1050409@logix-tt.com>	<1159798965.5314.58.camel@panoramix>
	<45212A20.60204@logix-tt.com>
	<17697.12636.485617.56760@gargle.gargle.HOWL>
	<454C7E77.3060706@logix-tt.com>
Message-ID: <loom.20070120T161007-100@post.gmane.org>

Markus Schaber <schabi <at> logix-tt.com> writes:

> 
> Hi, Matthias,
> 
> Matthias Klose wrote:
> 
> >> So it should be reassigned to pljava.
> 
> Somehow, the but reassignment did not work. Matthias, can you try it?
> 
> >> However, I read the Debian Changes of libgcj, and did not find any clear
> >> mentioning of why and how that was changed.
> > 
> > these are changes pulled from gcc-4.2/classpath-0.92. JNI_CreateJavaVM
> > can be found in libjvm.
> 
> So it seems we need to change the linker flags in the Makefile, right?
> 
> > Note that it's not necessary anymore to include the precompiled jar
> > file in the library.
> 
> Personally, I see it as an advantage to have the precompiled jar
> included in the library, that eases deployment.
> 
> > Building native code using dh_nativejava and/or
> > aot-compile should be used instead.
> 
> dh_nativejava would be ugly for upstream, it will only fix the problem
> for deban users, I presume?
> 
> > Documentation pending ...
> 
> Any progress here?
> 
> Thanks,
> Markus

I read the description of the dh_nativejar command:
it can compile jar to native binary.
But what about pljava.so, using C for JNI code?
Could you tell me precisely how to modify the makefile for pljava.so 
in order to
solve this problem.
I can add the problem is not specific to amd64 but occurs also 
on Debian Etch i386:
I have the same problem with the following configuration:
uname -a
Linux acoeur-e 2.6.18-3-k7 #1 SMP Mon Dec 4 17:23:11 UTC 2006 i686 GNU/Linux

regards,
Christophe