From: Glen Fullmer-EGF002 <Glen_Fullmer-EGF002@email.mot.com>
To: khan@xraylith.wisc.edu
Cc: Glen Fullmer-EGF002 <Glen_Fullmer-EGF002@email.mot.com>,
gnu-win32@cygnus.com
Subject: Re: dll, java, gcc, cygwin
Date: Sat, 24 Oct 1998 03:21:00 -0000 [thread overview]
Message-ID: <199810240216.VAA06954@emerald.ccrl.mot.com> (raw)
In-Reply-To: <Pine.SUN.3.93.981022223050.21375B-100000@modi.xraylith.wisc.edu>
Hello all,
>>>>> "MK" == Mumit Khan <khan@xraylith.wisc.edu> writes:
MK> Whenver loading fails, and you know that it's there, it's typically a
MK> question of calling the correct "name". For my applications, my load
MK> routines check for "foo" and "_foo" when asked to load "foo" to avoid
MK> MSVC vs GCC symbol naming issues.
I notice the difference between the ones that load and those that don't.
Andrew Mickish's .def has entries in name=name@nn form while yours has them
in name@nn form. When I changed yours to the former and changed the printf
to Andrew's jprintf it works too. It would be very nice if dlltool was
documented. I keep trying to guess what the syntax means!
Andrew mentions another gotcha. He says that printf will not work because
stdout is not accessible from cygwin's gcc/g++? Is that correct? It
definitely crashes with a printf in there on the NT box, but on the Sun
and HP we use gcc/g++ also and have no problem executing printf in our JNI
code. On those machines there is a problem calling printf in routines that
the JNI calls, but in the JNI code itself, it seems to work fine. What is
the difference? I noticed your code doesn't use jprintf like Andrew's.
How come?
MK> Are you creating .def files yourself? Are you checking to make sure
MK> that the decoration is correct (stdcall attribute adds those pesky
MK> @[num] at the end of symbols?
No, I let your dllwrap do it. It creates the name@nn form, and then I go
back and change it to the name=name@nn form by hand and run the stuff that
dllwrap would have done after the .def is created.
Thanks,
Glen.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next prev parent reply other threads:[~1998-10-24 3:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-21 10:06 Glen Fullmer-EGF002
1998-10-23 0:05 ` Andrew Mickish
1998-10-24 14:15 ` Mumit Khan
1998-10-23 6:03 ` Mumit Khan
1998-10-24 3:21 ` Glen Fullmer-EGF002 [this message]
1998-10-23 23:07 Philip A. Larson
1998-10-24 10:29 ` John A. Turner
1998-10-25 6:39 Earnie Boyd
1998-10-25 9:45 ` Mumit Khan
1998-10-25 20:17 Philip A. Larson
[not found] <Pine.SUN.3.93.981026173739.25460B-100000@modi.xraylith.wisc.edu>
1998-10-26 16:05 ` Glen Fullmer-EGF002
1998-10-28 0:40 Earnie Boyd
1998-10-27 15:02 ` Mumit Khan
1998-10-29 8:16 ` Glen Fullmer-EGF002
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199810240216.VAA06954@emerald.ccrl.mot.com \
--to=glen_fullmer-egf002@email.mot.com \
--cc=gnu-win32@cygnus.com \
--cc=khan@xraylith.wisc.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).