From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by walapai.inria.fr (8.13.6/8.13.6) with ESMTP id pBEGgm1C008704 for ; Wed, 14 Dec 2011 17:42:48 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AkUBAD7R6E7RVde2kGdsb2JhbABDhQimFwgiAQEBAQkJDQcUBCGBcgEBAQQSAg8dATcCAwwBBQUYCRYLAgIJAwIBAgEiAQUBHBMGAgEBFwehcwqLHIMzhRCJMQIFC4NuhHaCBIEWBI4agRaFRIVNgTSGdD2BTYIs X-IronPort-AV: E=Sophos;i="4.71,353,1320620400"; d="vcf'?scan'208";a="123369597" Received: from mail-ey0-f182.google.com ([209.85.215.182]) by mail4-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 14 Dec 2011 17:42:42 +0100 Received: by mail-ey0-f182.google.com with SMTP id f13so1712449eaa.27 for ; Wed, 14 Dec 2011 08:42:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:x-enigmail-version:content-type; bh=iVVMU++dh2n5Lh6bGCSqpjMaZdIH8H9Y5n4sWpH8nkQ=; b=Es0j4ML0r7wKTeb13xHgMqAG8JWGU1m4201ZnYQx7DSINbfiCJMy4rDHuYyjJT55Z4 B+MKVP509Y1Sus8k/2RpLulinCan4jEoYJgUvkB1Kcy4RGbGBpM9rwnJaefaykDHWEnP UypfXPX6+O0nVz4GmnCxp+13wVDyMfzHtycKw= Received: by 10.180.0.100 with SMTP id 4mr6109793wid.48.1323880962208; Wed, 14 Dec 2011 08:42:42 -0800 (PST) Received: from [128.93.60.63] (koch-irill.inria.fr. [128.93.60.63]) by mx.google.com with ESMTPS id eg7sm4293999wib.8.2011.12.14.08.42.40 (version=SSLv3 cipher=OTHER); Wed, 14 Dec 2011 08:42:41 -0800 (PST) Sender: Fabrice Le Fessant Message-ID: <4EE8D1FF.9000200@inria.fr> Date: Wed, 14 Dec 2011 17:42:39 +0100 From: Fabrice Le Fessant User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110922 Lightning/1.0b2 Thunderbird/3.1.15 MIME-Version: 1.0 To: caml-list@inria.fr References: <4EDE33A0.6070004@gmail.com> <1323760512.9833.9.camel@samsung> <4EE711FB.5020602@frisch.fr> <4EE83C26.7090108@frisch.fr> <4EE86D90.6080409@gmail.com> <4EE87976.4030604@frisch.fr> <1323876479.7750.36.camel@samsung> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: multipart/mixed; boundary="------------060400090704090006060700" X-Validation-by: fabrice.le_fessant@inria.fr Subject: Re: [Caml-list] Some comments on recent discussions This is a multi-part message in MIME format. --------------060400090704090006060700 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit A solution that I used is to patch OCaml to read a configuration file at startup. This configuration file overrides what was put in the config at compile time, so that you can change what C compiler/assembler/linker you use at every execution. It was done in a first attempt to build a cross-compiling compiler. Then, you can provide a simple tool that tests the environment and generate the corresponding configuration file. --Fabrice On 12/14/2011 04:49 PM, Adrien wrote: > On 14/12/2011, Gerd Stolpmann wrote: >> Am Mittwoch, den 14.12.2011, 14:37 +0100 schrieb Adrien: >>> On 14/12/2011, Alain Frisch wrote: >>>> As a concrete problem, until a few days ago, the mingw port could not be >>>> used with recent versions of Cygwin without some small hacks (like >>>> copying manually /bin/gcc-3.exe into gcc.exe, and passing more >>>> directories to flexlink). No big deal, but it can discourage beginners. >>> >>> Actually, I think that you should have used the "/etc/alternatives" >>> symlinks: /usr/bin/gcc points to /etc/alternatives/FOO and you can make >>> this >>> FOO symlink point to the /usr/bin/BAR binary that you want. >> >> There are no (usable) symlinks in Windows. Cygwin includes an emulation, >> but it is not understood by win32 programs, and hence this mechanism is >> unavailable for ocamlc/opt and flexlink. > > Hmmm, right. But if /usr/bin/gcc is already a symlink, ocaml wouldn't be > able to use it at all... I find it quite weird but I don't have a cygwin box > to test. > > But windows actually has symlinks. Kind of. Starting with Vista and the > corresponding NTFS version. But by default you need to be an administrator > to use them, you can only create a limited number of symlink in a given > folder afaiu, some functions work on the symlink and some on the target > (stat()/lstat()). They have a number of limitations and last time I looked > at them, I found them to be mostly unusable because of their limitations. > > They're one quite big issue I've had for packages on windows: if I > cross-compile a library from Linux, and make a tarball which has a number of > symlink in it. What to do when untarring on windows? Try to create symlinks? > Use hardlinks when possible? Copy the file's contents? Something else? > > Regards, > Adrien Nader > --------------060400090704090006060700 Content-Type: text/x-vcard; charset=utf-8; name="fabrice_le_fessant.vcf" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="fabrice_le_fessant.vcf" begin:vcard fn:Fabrice LE FESSANT n:LE FESSANT;Fabrice org:INRIA Saclay -- Ile-de-France;P2P & OCaml adr;quoted-printable:;;Parc Orsay Universit=C3=A9 ;Orsay CEDEX;;91893;France email;internet:fabrice.le_fessant@inria.fr title;quoted-printable:Charg=C3=A9 de Recherche tel;work:+33 1 74 85 42 14 tel;fax:+33 1 74 85 42 49 url:http://fabrice.lefessant.net/ version:2.1 end:vcard --------------060400090704090006060700--