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

[Etienne M. G. <eti...@uq...>]

Hi Grzegorz,

Grzegorz Prokopski wrote:
> Hi!
> 
> I am back from (longer) vacations. I packaged sablevm 1.0.4.
> 
> Just for the record - "it" happens in 1.0.4 version too.
> 
> But I think I may now know what's happening.
> After installing 1.0.3 I strace shows things like this:
> 
> open("/usr/lib/sablevm/libclasspath-1.0.1.so", O_RDONLY) = -1 ENOENT (No
> such file or directory)
> 
> Note 1.0.1 number there! - no such file exists!
> 
> When I am trying to use 1.0.4 it searches for libclasspath-1.0.3.so
> and other *1.0.3* files which don't exist!
> 
> The question now is: am *I* messing sth? I couldn't find any "1.0.3"
> string in sources of nativelib or sablevm. Anyway - the facts I can
> observe are above.
> 
> Hits?

The package version is managed by automake/autoconmf/build scripts.  Presumably, 
you are not using an *unmodified* SableVM "build" script, so I guess your 
modified build procedure has some problems.

You *must* rebuild all 3 sablevm[-*-library] packages for every new SableVM release.

The symbolic links are made in part by autoconf scripts and in part by the 
"build" script.

You are right on the fact that there is no version *embedded* into the source 
code: this is exactly what the author wanted, for easier maintenance. :)

Etienne

-- 
Etienne M. Gagnon                    http://www.info.uqam.ca/~egagnon/
SableVM:                                       http://www.sablevm.org/
SableCC:                                       http://www.sablecc.org/