From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr 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 094427EEB9 for ; Mon, 26 Oct 2015 09:25:12 +0100 (CET) IronPort-PHdr: 9a23:zj5uERGlxl6Ri8T1SDgANJ1GYnF86YWxBRYc798ds5kLTJ74psmwAkXT6L1XgUPTWs2DsrQf27eQ6virADZbqb+681k8M7V0HycfjssXmwFySOWkMmbcaMDQUiohAc5ZX0Vk9XzoeWJcGcL5ekGA6ibqtW1aJBzzOEJPK/jvHcaK1oLsh730osWYOl8TzBOGIppMbzyO5T3LsccXhYYwYo0Q8TDu5kVyRuJN2GlzLkiSlRuvru25/Zpk7jgC86l5r50IAu3GePEURKJZAHwPN2Qu49Xz/U3PVwLK4HYDSU0TnwZBGBTM5xK8VZD05G+y/OF03S3fOcztUZg1Xy6j5uFlUlWg3CwOMjp89GDMluRxirhaqVSvvUos7ZTTZdTfD/1zcb/HesteDU9AVcZYWigLSte5boAPBucFe/1foobhvVwWhRq4GQSoQujoz2kb1TfNwaQm3rF5Qkn91ws6EodWvQ== Authentication-Results: mail3-smtp-sop.national.inria.fr; spf=None smtp.pra=michael.soegtrop@intel.com; spf=Pass smtp.mailfrom=michael.soegtrop@intel.com; spf=None smtp.helo=postmaster@mga02.intel.com Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of michael.soegtrop@intel.com) identity=pra; client-ip=134.134.136.20; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="michael.soegtrop@intel.com"; x-sender="michael.soegtrop@intel.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of michael.soegtrop@intel.com designates 134.134.136.20 as permitted sender) identity=mailfrom; client-ip=134.134.136.20; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="michael.soegtrop@intel.com"; x-sender="michael.soegtrop@intel.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mga02.intel.com) identity=helo; client-ip=134.134.136.20; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="michael.soegtrop@intel.com"; x-sender="postmaster@mga02.intel.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0BAAAAC4y1WnBSIhoZdhApvBr43AQ0jgTcZhgQCgSM4FAEBAQEBAQEBEAEBAQEBBg0JCSEugiuCBwEBAQMBOg81CwIBCA4CAhAUEDIXAQ0BAQQBGoggBwHEEgEBAQcBAQEBAR6GeYR8hFw4gxqBFAWWNgGeYYpvHwEBgmmBXHKGEoEGAQEB X-IPAS-Result: A0BAAAAC4y1WnBSIhoZdhApvBr43AQ0jgTcZhgQCgSM4FAEBAQEBAQEBEAEBAQEBBg0JCSEugiuCBwEBAQMBOg81CwIBCA4CAhAUEDIXAQ0BAQQBGoggBwHEEgEBAQcBAQEBAR6GeYR8hFw4gxqBFAWWNgGeYYpvHwEBgmmBXHKGEoEGAQEB X-IronPort-AV: E=Sophos;i="5.20,200,1444687200"; d="scan'208";a="151737080" Received: from mga02.intel.com ([134.134.136.20]) by mail3-smtp-sop.national.inria.fr with ESMTP; 26 Oct 2015 09:25:10 +0100 Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga101.jf.intel.com with ESMTP; 26 Oct 2015 01:25:07 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,200,1444719600"; d="scan'208";a="819426255" Received: from irsmsx152.ger.corp.intel.com ([163.33.192.66]) by fmsmga001.fm.intel.com with ESMTP; 26 Oct 2015 01:25:06 -0700 Received: from irsmsx102.ger.corp.intel.com ([169.254.2.98]) by IRSMSX152.ger.corp.intel.com ([169.254.6.38]) with mapi id 14.03.0248.002; Mon, 26 Oct 2015 08:25:01 +0000 From: "Soegtrop, Michael" To: David Allsopp , "caml-list@inria.fr" Thread-Topic: [Caml-list] Effect of Windows LLP64 architecture on 64 bit MingW OCaml Thread-Index: AdENmsKQlrGb4SdjTW+mxn2nfuieSgACo8EAACYH9CAAAuWq8ABe4vPg Date: Mon, 26 Oct 2015 08:25:00 +0000 Message-ID: <0F7D3B1B3C4B894D824F5B822E3E5A172CE33594@IRSMSX102.ger.corp.intel.com> References: <0F7D3B1B3C4B894D824F5B822E3E5A172CE32E38@IRSMSX102.ger.corp.intel.com> <562A5C92.50206@inria.fr> <0F7D3B1B3C4B894D824F5B822E3E5A172CE3315A@IRSMSX102.ger.corp.intel.com> In-Reply-To: Accept-Language: de-DE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: RE: [Caml-list] Effect of Windows LLP64 architecture on 64 bit MingW OCaml Dear David, > FWIW, this might be pulling itself into my native Windows OPAM port - we'= re > interested in Windows/Cygwin cross-compilers (i.e. ocamlopt being a Cygwin > executable which outputs native Windows executables using mingw64/msvc > and vice versa) and it makes sense to unify the build process at the same > time as trying to do that. I fully agree. But I think full native windows Ocaml compilers are also req= uired. E.g. recent Coq requires an Ocaml compiler at run time and one doesn= 't want to require Cygwin for this. That's the reason why I started to thin= k what it would take to get to a gcc like configure with separate build, ho= st and target configure parameters. In the end one might want to have 3 dif= ferent build variants: -build=3Dx86_64-pc-cygwin -host=3D x86_64-pc-cygwin -target=3Dx86_64-pc-cygwin As far as I can tell this variant works fine and also opam works in this co= nfiguration out of the box. Useful for people working on GPL projects or ca= n afford a lawyer to figure out the licensing details or a want to buy a cy= gwin commercial license. -build=3Dx86_64-pc-cygwin -host=3D x86_64-pc-cygwin -target=3Dx86_64-w64-mingw32 This is what you mentioned above and, assuming opam works, would be a good = work for environment for everybody who is mostly working on Linux and just = wants to supply Windows binaries of his application with minimal effort. -build=3Dx86_64-pc-cygwin -host=3Dx86_64-w64-mingw32 -target=3Dx86_64-w64-mingw32 This works by using the supplied separate makefiles and is required for tho= se who mainly work on Windows and for applications which need an Ocaml comp= iler at run time (like Coq 8.5). Best regards, Michael Intel Deutschland GmbH Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany Tel: +49 89 99 8853-0, www.intel.de Managing Directors: Christin Eisenschmid, Prof. Dr. Hermann Eul Chairperson of the Supervisory Board: Tiffany Doon Silva Registered Office: Munich Commercial Register: Amtsgericht Muenchen HRB 186928