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

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

W li=B6cie z czw, 22-08-2002, godz. 00:52, Mark Wielaard pisze:=20
> I haven't yet figured out why that is but this is progress. And when I
> copy Hello.class to /usr/local/sablevm/lib/sablevm/classes-1.0.1/
> I get:
> mark@multatuli:~$ /usr/local/sablevm/bin/sablevm-debug -Y Hello
> Hello World!
Congrats!!!

> Yeah! If "Hello World" is possible everything else should be possible :)
Yes, that means we're "almost there" (-:

Huh, I think in such way we'll have 12 architectures by the end of this
year very easily. I think everybody understand, that this would be major
step towards wider acceptance of sablevm as "The Free JVM".

> I am very happy because this means that there might be some issues on
> PowerPC but it seems there is not something major wrong.
Yeah - I was worried a bit about PowerPC being hi-endian, but now you
prove my worries to be unnecessary ;-)

> Hopefully I will have some time this weekend to clean up what I have and
> look at where/why the valid() really fails and why my sablevm cannot
> find anything besides inside its own bootclasspath directory.
I hope debian admins will finally install those -dev packages I asked
for ;-) It takes them forever to do this. If it's like this for longer
time - I'll compile and install them in my home dir, but that's
hackish and errorprone.

Today sablevm-classlib and sablevm-nativelib were accepted into archive,
but unfortunatelly I overlooked some bit in sablevm and it got rejected
(first time in my history) so it will take a moment longer.
Anyway - it seems that the porting effort can be made a bit more
"blindly" - the we can go by simply uploading "blindly ported" packages,
letting autobuilders play with them and waiting for bugreports.
We'll see.

Summarizing: WoW! - thanks for the happy news!

Best regards

					GBP