From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.1.3 Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by yquem.inria.fr (Postfix) with ESMTP id A3A6ABC6B for ; Sun, 26 Aug 2007 15:55:19 +0200 (CEST) Received: from server2.thinkcrime.de (server2.thinkcrime.de [213.133.110.149]) by concorde.inria.fr (8.13.6/8.13.6) with ESMTP id l7QDtJGE023126 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Sun, 26 Aug 2007 15:55:19 +0200 Received: from hod-sarge-2005-10.lan.m-e-leypold.de (dslb-088-074-032-182.pools.arcor-ip.net [88.74.32.182]) (Authenticated sender: hod-sarge-2005-10@server2) by server2.thinkcrime.de (Postfix) with ESMTP id E06A290015C for ; Sun, 26 Aug 2007 15:55:05 +0200 (CEST) Received: by hod-sarge-2005-10.lan.m-e-leypold.de (Postfix, from userid 1003) id 8907237BD0; Sun, 26 Aug 2007 16:07:18 +0200 (CEST) To: caml-list@inria.fr Subject: MingW compiler (!) and Ocaml for Windows From: Markus E L Organization: N/A Date: Sun, 26 Aug 2007 16:07:18 +0200 Message-ID: User-Agent: Some cool user agent (SCUG) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Miltered: at concorde with ID 46D18647.009 by Joe's j-chkmail (http://j-chkmail . ensmp . fr)! X-Spam: no; 0.00; mingw:01 compiler:01 ocaml:01 markus:01 mingw:01 cygwin:01 ocaml-:01 ocamlopt:01 gcc:01 lablgtk:01 ocamlopt:01 occuring:01 cygwin:01 markus:01 ocaml:01 Hi Caml riders, I'd like to ask wether anybody knows about the status of using the native Win32 port built with Mingw with the standalone MingW compilers instead of the Cygwin/MingW compilers. Until recently my state of awareness was what's been written in http://caml.inria.fr/pub/distrib/ocaml-3.10/notes/README.win32: "Do *not* install the Mingw/MSYS development tools from www.mingw.org: these are not compatible with this Caml port (@responsefile not recognized on the command line)." Rather accidentally (sourced wrong paths :-) I recently used MinGW compilers with ocamlopt -- and it worked! I was only partially suprised, since I've seen patches to MingW gcc floating around (something like one and a half year ago) that added the "@responsefile" feature. Since then I tested a bit more (only with relatively small programs but also with lablgtk) and it worked for me every time. Now the question: Would I see the "@responsefile" problem on the first attempt or are response files only used in certain situations I perhaps haven't met yet? Can anybody say anything on wether ocamlopt now works with the MingW compilers (or better wether the MingW compilers now work with ocamlopt)? If on the other side problems with "@responsefile" are only occuring in more rare situation -- can anybody tell me how to provoke the problem? (Then I'd perhaps be suffieciently interested to try in the long run to port the missing features from CygWin/MingW to standalone MingW). Regards - Markus PS: I'm using a recent "stable" MingW and the MingW build of ocaml 3.09.