> now I'm thinking about dead-lock related to STDLIB
> initialization routines (possibly coming from(?) <stdio.h>).
I've tried this and confirmed that, if I simply say:
--
% cl -Ic:\java\include -Ic:\java\include\win32
-LD MyProg.c -FeMyProg.dll
--
(as in the java tutorial at
http://java.sun.com/docs/books/tutorial/native1.1/stepbystep/step5.html)
things DOES hang, but if I say this instead:
--
% cl -Ic:\java\include -Ic:\java\include\win32 -c MyProg.c
% link /dll /nodefaultlib /out:MyProg.dll MyProg.obj %MSC%\lib\MSVCRT.LIB
%MSC%\lib\kernel32.lib
--
the created DLL now doesn't hang the JVM and
works just fine.
-I still don't think the above command lines are
optimal, but anyway this appears to be the _problem_ :)
kenji
ps., does any service pack updates fix this automatically?
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
