From: "Török Edwin" <edwin+ml-ocaml@etorok.net>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Re: portable truncate
Date: Sat, 27 Jul 2013 23:03:42 +0300 [thread overview]
Message-ID: <51F4279E.1090603@etorok.net> (raw)
In-Reply-To: <20130727195328.GA32686@notk.org>
On 07/27/2013 10:53 PM, Adrien Nader wrote:
> On Sat, Jul 27, 2013, Florent Monnier wrote:
>> 2013/7/27, Adrien Nader wrote:
>>> On Sat, Jul 27, 2013, Florent Monnier wrote:
>> [...]
>>>> mingw's additional lib has to be used if we're using thread for
>>>> example if I have understood correctly.
>>>
>>> What makes you think so?
>>
>> The sentence below that is on the website of the project:
>>
>> "It does depend on a number of DLLs provided by Microsoft themselves,
>> as components of the operating system; most notable among these is
>> MSVCRT.DLL, the Microsoft C runtime library. Additionally, threaded
>> applications must ship with a freely distributable thread support DLL,
>> provided as part of MinGW itself"
>
> I'd be on it being outdated.
>
> The "pthreads" libraries on Windows are meant to ease porting of
> applications to Windows and I wouldn't be surprised that pthreads-win32
> had first been used for that. Then when thread support was finally
> implemented without requiring pthreads-win32, updating the documentation
> was of course forgotten. :-)
>
> That just an hypothesis but it seems likely enough for me.
>
There was a time when some MinGW-compiled applications depended on mingw10.dll that had to setup/cleanup something related to exceptions.
According to [1] in mingw-w64 this is no longer required because their runtime includes the required support:
I haven't used MinGW (or in fact Windows) since quite a long time so I don't know what the situation is today, but since mingw-w64 can build both 32 and 64-bit applications this is probably not an issue anymore.
http://sourceforge.net/apps/trac/mingw-w64/wiki/Feature%20list
--Edwin
next prev parent reply other threads:[~2013-07-27 20:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 10:35 [Caml-list] " Florent Monnier
2013-07-26 10:46 ` Mihamina Rakotomandimby
2013-07-26 10:48 ` Török Edwin
2013-07-26 10:52 ` Daniel Bünzli
2013-07-26 12:02 ` [Caml-list] " Florent Monnier
2013-07-27 7:05 ` David Allsopp
2013-07-27 8:54 ` Florent Monnier
2013-07-27 8:38 ` Adrien Nader
2013-07-27 9:05 ` Adrien Nader
2013-07-27 14:11 ` Florent Monnier
2013-07-27 14:23 ` Adrien Nader
2013-07-27 15:34 ` Florent Monnier
2013-07-27 15:43 ` Adrien Nader
2013-07-27 19:45 ` Florent Monnier
2013-07-27 19:53 ` Adrien Nader
2013-07-27 20:03 ` Török Edwin [this message]
[not found] ` <20130727181711.65d8456f@kiwi.local.tld>
2013-07-27 14:41 ` [Caml-list] " Florent Monnier
2013-07-27 15:26 ` Adrien Nader
2013-07-27 15:40 ` Florent Monnier
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=51F4279E.1090603@etorok.net \
--to=edwin+ml-ocaml@etorok.net \
--cc=caml-list@inria.fr \
/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