This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
RE: input line is too long
- From: "Erik Poupaert" <erik dot poupaert at chello dot be>
- To: <tromey at redhat dot com>
- Cc: <java at gcc dot gnu dot org>
- Date: Wed, 1 Jan 2003 07:47:36 +0100
- Subject: RE: input line is too long
Erik> If the lookup fails, we could ask natruntime.cc to continue
Erik> querying, but then from the executable's own symbols and try to
Erik> resolve the JNI symbol's address from there?
>>> We already do this when possible.
>>> See Runtime.init().
You're right; and in fact, he does manage to find the JNI symbols. It is
another series of symbols he fails to find. In the win32 makefile of
swt-xxx.dll, I can see that:
LINK_LIBS = ole32.lib comctl32.lib user32.lib gdi32.lib comdlg32.lib
kernel32.lib shell32.lib oleaut32.lib advapi32.lib imm32.lib winspool.lib
oleacc.lib
The missing symbols are undoubtedly from there.
I will try to link the resulting executable against these "LINK_LIBS" as
well. By the way, I can see that minGW/gcc has very similar symbolic(?)
libraries it its lib folder. ole32.lib is probably libole32.a, and so on.
This native stuff is daunting. Let me have another intergalactic war with
it!
Happy New Year
Erik