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

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

Grzegorz Prokopski wrote:
> my build procedure for all the packages is simple: 
> ./configure; make; make install 
> with options about where put what - that's all 
> no magic at all 

You're not giving any argument to "configure"?  This won't work unless you're 
installing into /usr/local.  This might be your problem.  "configure" must be 
given the exact installation directory names (try configure --help).

> 
> So where do these numbers come from then? 

From:

1) configure.ac
2) build[-*] scripts (variable VERSION)

and (as a consequence of the above 1 & 2):

3) files generated by autoconf/automake: [*/]Makefile.in configure
4) files generated by "configure": [*/]/Makefile

> 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]:
>... 
> 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?

Check your build procedures, in light of the above information.

> 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).

I thought automake/autoconf were pretty much standard GNU tools... The only 
SableVM specific stuff is the "build" script.  The remaining is more/less 
standard auto* stuff.

Of course, you must always restart with a *fresh* working directory.  If you had 
any leftover files from a previous installation (in your working directory), 
auto* tools might behave strangely.

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

Maybe, but you haven't convinced me yet. :-)

> 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 :-/

Don't forget to be very friendly with our great fiends the ftpmasters.  They 
like to feel important and respected... ;-)))

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