From: "HENRIKSON, JEFFREY" <JEFHEN@SAFECO.com>
To: "Peter Jolly" <peter@jollys.org>
Cc: <caml-list@inria.fr>
Subject: RE: [Caml-list] mingw dll hell
Date: Fri, 27 Feb 2004 15:57:19 -0800 [thread overview]
Message-ID: <9410EC84C0872141B27A2726613EF45D02A52CEB@psmrdcex01.psm.pin.safeco.com> (raw)
Hmm, thank you I didn't know about cygcheck. I am accustomed to using
ldd under linux.
$ cygcheck test.exe
Found: .\test.exe
Found: C:\cygwin\bin\test.exe
test.exe
C:\WINNT\system32\msvcrt.dll
C:\WINNT\system32\KERNEL32.dll
C:\WINNT\system32\ntdll.dll
I'd love to observe the crash, but the program doesn't print the first
line and gdb makes the bug go away.
Jeff Henrikson
-----Original Message-----
From: Peter Jolly [mailto:peter@jollys.org]
Sent: Friday, February 27, 2004 3:42 PM
To: HENRIKSON, JEFFREY
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] mingw dll hell
> One thing I seem to be noticing is that there are fewer errors if I
> do not link to libraries that depend on cygwin1.dll.
While I can't explain why it worked before, in general it's an extremely
bad idea to mix MinGW and Cygwin in the same program. If you're using
gcc -mno-cygwin in the build process, you should not be linking to any
Cygwin libraries at all.
As a simple test, run cygcheck on the generated executable. If it lists
both cygwin1.dll and MSVCRT*.DLL among the dependencies, you are almost
certain to have problems.
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next reply other threads:[~2004-02-27 23:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-27 23:57 HENRIKSON, JEFFREY [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-27 22:50 HENRIKSON, JEFFREY
2004-02-27 23:42 ` Peter Jolly
2004-02-22 23:04 Jeff Henrikson
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=9410EC84C0872141B27A2726613EF45D02A52CEB@psmrdcex01.psm.pin.safeco.com \
--to=jefhen@safeco.com \
--cc=caml-list@inria.fr \
--cc=peter@jollys.org \
/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 NNTP newsgroup(s).