Hi Mark,
Mark Wielaard wrote:
On Mon, 2005-08-01 at 23:29 +0200, Andreas Tobler wrote:
Well, I will investigate a bit more. But my guess is here:
with jamvm and other vm you run interpreted code, where the classpath
lib is the last bit in the chain. On gcj/libgcj you can build/run native
apps where you link the libgcj against the app. As mentioned above, you
can not link against a module on darwin.
But as said, I will provide some more details later. Also some tests. It
may has also to do with the class loading mechanism.
Btw, I also successfully ran cp with jamvm :)
Well, here I should have said 'once', with the actual cp I didn't. :(
But I know jamvm will fail because it in src/dll.c:300 it checks against
.so and new will .dylib on darwin.
Sorry for not being more clear.
OK, so it seems a positive change in all cases, at least for you. Then
it is probably a good idea to commit it now and see if anybody that
tests CVS on darwin yells and screams.
I will investigate later today and hopefully I'll be prepared for any
compliants.
Thanks,
Andreas
_______________________________________________
Classpath-patches mailing list
Classpath-patches@gnu.org
http://lists.gnu.org/mailman/listinfo/classpath-patches
