From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id B850081799 for ; Sat, 27 Jul 2013 22:03:44 +0200 (CEST) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of edwin+ml-ocaml@etorok.net) identity=pra; client-ip=176.9.138.55; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="edwin+ml-ocaml@etorok.net"; x-sender="edwin+ml-ocaml@etorok.net"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of edwin+ml-ocaml@etorok.net designates 176.9.138.55 as permitted sender) identity=mailfrom; client-ip=176.9.138.55; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="edwin+ml-ocaml@etorok.net"; x-sender="edwin+ml-ocaml@etorok.net"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of postmaster@mail.etorok.net designates 176.9.138.55 as permitted sender) identity=helo; client-ip=176.9.138.55; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="edwin+ml-ocaml@etorok.net"; x-sender="postmaster@mail.etorok.net"; x-conformance=sidf_compatible; x-record-type="v=spf1" X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhgFAFAn9FGwCYo3/2dsb2JhbABbgmUhNYNfukeBGhZ0giQBAQUjHQEBNgIPCxgCAgUWCwICCQMCAQIBNwENEwgCiA0DCKYSdINOAQWNIQaBKI5cFoJNgSKJJ447gSmQI4MX X-IPAS-Result: AhgFAFAn9FGwCYo3/2dsb2JhbABbgmUhNYNfukeBGhZ0giQBAQUjHQEBNgIPCxgCAgUWCwICCQMCAQIBNwENEwgCiA0DCKYSdINOAQWNIQaBKI5cFoJNgSKJJ447gSmQI4MX X-IronPort-AV: E=Sophos;i="4.89,758,1367964000"; d="scan'208";a="22477090" Received: from mail.etorok.net ([176.9.138.55]) by mail3-smtp-sop.national.inria.fr with ESMTP; 27 Jul 2013 22:03:43 +0200 Received: from [IPv6:2a02:2f09:4061:1400:81b2:feb8:91a2:5a31] (unknown [IPv6:2a02:2f09:4061:1400:81b2:feb8:91a2:5a31]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.etorok.net (Postfix) with ESMTPSA id AF45D46DB for ; Sat, 27 Jul 2013 22:03:42 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=etorok.net; s=mailout; t=1374955422; bh=c4jDUT9RMVP1yBURVLu5GhUfZ9Q/zzzpEUSwPmESWIo=; l=1716; h=Date:From:To:References:In-Reply-To:From; b=GRJSeX6Sy4pBzK1HDcnxAVKgy7nJZAOTA+UPqN8Q4mqli7/xUbivZuNvQUQ3W/2FW bIje56lGMrkiCMBuNPxd+/jT4esb2XNsJbPBM99CmL9hAYdPN/NQCPTcLuiaLXA0k9 3V3hrGLgIKfG9AlagxrvxoDcfIPkVQHOpe+82JQo= Message-ID: <51F4279E.1090603@etorok.net> Date: Sat, 27 Jul 2013 23:03:42 +0300 From: =?UTF-8?B?VMO2csO2ayBFZHdpbg==?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130630 Icedove/17.0.7 MIME-Version: 1.0 To: caml-list@inria.fr References: <20130727083844.GA17235@notk.org> <20130727142320.GA26244@notk.org> <20130727154347.GA3385@notk.org> <20130727195328.GA32686@notk.org> In-Reply-To: <20130727195328.GA32686@notk.org> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.97.8 at mail X-Virus-Status: Clean Subject: Re: [Caml-list] Re: portable truncate 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