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 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by yquem.inria.fr (Postfix) with ESMTP id E1115BBAF for ; Wed, 15 Oct 2008 17:30:56 +0200 (CEST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AmoDAM+p9UhDz4HeiGdsb2JhbACTYAEBARUirX2Baw X-IronPort-AV: E=Sophos;i="4.33,417,1220220000"; d="scan'208";a="30374645" Received: from discorde.inria.fr ([192.93.2.38]) by mail4-smtp-sop.national.inria.fr with ESMTP; 15 Oct 2008 17:30:56 +0200 Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by discorde.inria.fr (8.13.6/8.13.6) with ESMTP id m9FFUs2h021567 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=OK) for ; Wed, 15 Oct 2008 17:30:56 +0200 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AmoDAM+p9UhDz4HeiGdsb2JhbACTYAEBARUirX2Baw X-IronPort-AV: E=Sophos;i="4.33,417,1220220000"; d="scan'208";a="30374625" Received: from fettunta.fettunta.org ([67.207.129.222]) by mail4-smtp-sop.national.inria.fr with ESMTP; 15 Oct 2008 17:30:34 +0200 Received: from usha.takhisis.invalid (unknown [10.17.0.18]) by fettunta.fettunta.org (Postfix) with ESMTP id 90C4B18126 for ; Wed, 15 Oct 2008 15:30:32 +0000 (UTC) Received: by usha.takhisis.invalid (Postfix, from userid 1000) id 494B8688C; Wed, 15 Oct 2008 17:29:17 +0200 (CEST) Date: Wed, 15 Oct 2008 17:29:17 +0200 From: Stefano Zacchiroli To: caml users Subject: Re: [Caml-list] OCaml version 3.11.0+beta1 Message-ID: <20081015152917.GA13876@usha.takhisis.invalid> Mail-Followup-To: caml users References: <83E04F95-55DD-470E-9C6D-98FA15AE0CE0@inria.fr> <1477A5A4-3533-4A62-AF02-07F860E56773@gmail.com> <48F6068E.70904@frisch.fr> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <48F6068E.70904@frisch.fr> User-Agent: Mutt/1.5.18 (2008-05-17) X-Miltered: at discorde with ID 48F60CAE.000 by Joe's j-chkmail (http://j-chkmail . ensmp . fr)! X-Spam: no; 0.00; zacchiroli:01 zack:01 ocaml:01 0200,:01 frisch:01 dynlink:01 dynlink:01 mingw:01 cygwin:01 packagers:01 cheers:01 zacchiroli:01 postdoc:01 zack:01 dietro:98 On Wed, Oct 15, 2008 at 05:04:46PM +0200, Alain Frisch wrote: > Andres Varon wrote: >> Thanks for the good work. I would like to know exactly what >> architectures support the native Dynlink? I did not see this >> information in the release notes. > The native Dynlink is known to work under Linux x86, Linux AMD64, Win32 > (mingw/msvc ports). It has been lightly tested under Win64, some flavors > of BSDs and also the Cygwin port. [ Sorry for being lazy to check by myself, but apparently the question is of wide-interest. ] Is that something that packagers should worry about or not? I mean, the specific modules/libraries/... are already detected by configure and not built/installed/... on architectures missing them or should we (packages) enforce that? Many thanks in advance (and for native Dynlink of course :-))! Cheers. -- Stefano Zacchiroli -*- PhD in Computer Science \ PostDoc @ Univ. Paris 7 zack@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/ Dietro un grande uomo c'è sempre /oo\ All one has to do is hit the right uno zaino -- A.Bergonzoni \__/ keys at the right time -- J.S.Bach