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=AWL autolearn=disabled version=3.1.3 Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by yquem.inria.fr (Postfix) with ESMTP id 2F970BC69 for ; Mon, 24 Dec 2007 11:40:49 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Ao8CAJobb0dQRFuw/2dsb2JhbACoCw X-IronPort-AV: E=Sophos;i="4.24,202,1196636400"; d="scan'208";a="5491089" Received: from furbychan.cocan.org ([80.68.91.176]) by mail2-smtp-roc.national.inria.fr with ESMTP; 24 Dec 2007 11:40:48 +0100 Received: from rich by furbychan.cocan.org with local (Exim 3.35 #1 (Debian)) id 1J6kjP-0000vf-00; Mon, 24 Dec 2007 10:40:23 +0000 Date: Mon, 24 Dec 2007 10:40:23 +0000 To: =?iso-8859-1?Q?M=E1rk_S=2E_Zolt=E1n?= Cc: Caml Mailing List Subject: Re: Re: [Caml-list] Re: MinGW port w/o Cygwin? Message-ID: <20071224104022.GA30047@furbychan.cocan.org> References: <200712200930.29585.ober.14@osu.edu> <87sl1xgzkp.fsf@pps.jussieu.fr> <200712201518.20487.ober.14@osu.edu> <90823c940712210606h24f7617eh4e20745cd3e4782a@mail.gmail.com> <476E7CA1.6000501@dravanet.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <476E7CA1.6000501@dravanet.hu> User-Agent: Mutt/1.5.13 (2006-08-11) From: Richard Jones X-Spam: no; 0.00; mingw:01 cygwin:01 0100,:01 mingw:01 ocaml:01 -mno-cygwin:01 compiler:01 cflags:01 23,:98 wrote:01 caml-list:01 conventions:02 authors:03 apps:04 problem:05 On Sun, Dec 23, 2007 at 04:20:01PM +0100, "Márk S. Zoltán" wrote: > I am using my clandestine MSys + MinGW OCaml since about 3.0, and I have > originally switched to MSys because the configuration scripts of a > number of other apps and libraries did not handle the -mno-cygwin flag, > or any other flag for that matter: the 'supply extra compiler flags' > feature seemed to be thoroughly broken in all configure scripts, I > wonder if anyone ever uses it. The problem is that configure.ac authors have to follow a series of arcane conventions to make sure they don't delete the user-specified CFLAGS. Since they don't, and there's no indication to the author that they have, it is often broken. But then the auto* tools are just terrible like this. Rich. -- Richard Jones Red Hat