Re: [Sablevm-developer] Problems with 1.0.3 - java/lang/UnsatisfiedLinkError

[Grzegorz P. <gr...@se...>]

W li=B6cie z pi=B1, 06-09-2002, godz. 15:19, Etienne M. Gagnon pisze:=20
> The package version is managed by automake/autoconmf/build scripts.  Pres=
umably,=20
> you are not using an *unmodified* SableVM "build" script, so I guess your=
=20
> modified build procedure has some problems.
my build procedure for all the packages is simple:=20
./configure; make; make install=20
with options about where put what - that's all=20
no magic at all=20

> You *must* rebuild all 3 sablevm[-*-library] packages for every new Sable=
VM release.
oh, sure I did !

> The symbolic links are made in part by autoconf scripts and in part by th=
e=20
> "build" script.
> You are right on the fact that there is no version *embedded* into the so=
urce=20
> code: this is exactly what the author wanted, for easier maintenance. :)
So where do these numbers come from then?=20

I removed all *sablevm* packages from my system, rebuilded, installed
and problem still looks the same. But that's false impression(!)
Now it looks for *1.0.4* libs where it should and finds them...
with one exception [1]:

open("/usr/lib/sablevm/libjava-lang-1.0.4.so", O_RDONLY) =3D -1 ENOENT (No
such file or directory)

How is that possible? don't know. But in just builded source tree I
don't find this file anymore (but it exists in builded 1.0.3 source
tree).

So now, having all sablevm (non-working) packages installed I rebuilded
'native'. Oh f*** - it worked! - libjava-lang-1.0.4.so has been created!

Of course after I install this new 'native' package - HelloWorld works
well w/o any tricks.

What would you say to that?

My first impression is that the build process is flawed somewhere, as
such things NEVER should take place, or at least should be very clearly
documented. I will workaround it by declaring bulid-conflicts of sablevm
with all sablevm packages and by build-depending of 'native' on
'sablevm' source resulting packages (no cyclic-build-deps).

So, I belive that it works in _your_ environment, but the bug is
somewhere there - don't you think?

Now I am gonna fix 1.0.4 packages and upload them to NEW queue with
the hope that ftpmasters will finally let it into the archive :-/

Cheers

						GBP

[1] I was building all 3 sources in separate directiries, simultanously
w/o having any sablevm binary/resulting package installed.