Does the file exist? Does it have appropriate permissions? Do all
the
dirs leading up to it have appropriate permissions?
It does. It has (it had - it worked). I can read them all - which
should be enough.
Are you running the JVM in 64-bit mode? I think not, because you
said it
fails on G5 PPC, and there isn't a 64-bit JVM for that CPU.
No. ooRexx is also 32 bit only.
There is no "/opt" directory by default, and if Leopard was
installed using
"Archive and Install" it may have moved aside something you may be
depending on.
It is still there.
I haven't noticed any breakages due to the JVM now accepting
".dylib" as a
secondary suffix. All the ".jnilib" files I have now still work.
And can anyone give me a pointer on how to use this nifty DTRACE
stuff to
see exactly which library filename MacOSX is trying to load?
I think it's already telling you the full pathname:
/opt/ooRexx/lib/libBSF4Rexx.jnilib
I was thinking the message might say something different from what it
actually tries to feed the dlopen() or equivalent api.
That's not a relative pathname. If it should be, then that's a
different
problem, caused by "." not being in the java.library.path search
order.
It is meant to be absolute. It should run on users systems without me
modifying java.library.path. I did not change my .tcshrc after the
upgrade and I expect an upgrade to work the same on an ooRexx user
machine.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
