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 pBEFnmnI006693 for ; Wed, 14 Dec 2011 16:49:49 +0100 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AkQBAFbE6E5KfVM2kGdsb2JhbABDqx8IIgEBAQEJCQ0HFAQhgXIBAQEEEgIsARsdAQMMBgULAwouIgERAQUBHAYTIqF2CotkgmuFF0CIcQIFC4NuiBAEjTuHOY11PYN5 X-IronPort-AV: E=Sophos;i="4.71,352,1320620400"; d="scan'208";a="123362205" Received: from mail-ee0-f54.google.com ([74.125.83.54]) by mail4-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 14 Dec 2011 16:49:43 +0100 Received: by mail-ee0-f54.google.com with SMTP id c50so1266995eek.27 for ; Wed, 14 Dec 2011 07:49:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=xRW8R3jvmIn2LO8sMRssFkQM+X03Mq8iRmV88/uslYg=; b=fpbp9ZaIB2DsuPMAvmoTTfOeFfSrEw9P18Hy6wKYckYx1AmmzGAEnQyazA+J8XiLgS xaYt2yChF+qRJJYFQclnPLXiQapqye7MRRNgItESXA8uo7XaKjsxAorGPkVnpTkpEiQl WtKLZaX2YUKg4YddQKnoMa+QbHgGCM410fR2k= MIME-Version: 1.0 Received: by 10.213.31.147 with SMTP id y19mr768123ebc.80.1323877783411; Wed, 14 Dec 2011 07:49:43 -0800 (PST) Received: by 10.213.10.148 with HTTP; Wed, 14 Dec 2011 07:49:43 -0800 (PST) In-Reply-To: <1323876479.7750.36.camel@samsung> 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> Date: Wed, 14 Dec 2011 16:49:43 +0100 Message-ID: From: Adrien To: Gerd Stolpmann Cc: Alain Frisch , Jonathan Protzenko , Martin DeMello , caml-list@inria.fr Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [Caml-list] Some comments on recent discussions 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