From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by yquem.inria.fr (Postfix) with ESMTP id 92921BBAF for ; Mon, 31 May 2010 12:04:17 +0200 (CEST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvMDAKsmA0zB/Bd4jmdsb2JhbACDGJsbFQEBAQEUCAkPBR+wH5AygSaDBWsE X-IronPort-AV: E=Sophos;i="4.53,332,1272837600"; d="scan'208";a="60322044" Received: from smtp-msa-out01.orange.fr ([193.252.23.120]) by mail1-smtp-roc.national.inria.fr with ESMTP; 31 May 2010 12:04:17 +0200 Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf5a04.orange.fr (SMTP Server) with ESMTP id 19B5D1C00945; Mon, 31 May 2010 12:04:17 +0200 (CEST) Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf5a04.orange.fr (SMTP Server) with ESMTP id 0796B1C0093F; Mon, 31 May 2010 12:04:17 +0200 (CEST) Received: from [192.168.1.90] (APuteaux-154-1-70-204.w81-249.abo.wanadoo.fr [81.249.113.204]) by mwinf5a04.orange.fr (SMTP Server) with ESMTP id BAA9F1C0093C; Mon, 31 May 2010 12:04:16 +0200 (CEST) X-ME-UUID: 20100531100416764.BAA9F1C0093C@mwinf5a04.orange.fr X-ME-User-Auth: lexifi Message-ID: <4C0389A2.40606@frisch.fr> Date: Mon, 31 May 2010 12:04:18 +0200 From: Alain Frisch User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4 MIME-Version: 1.0 To: =?UTF-8?B?U3TDqXBoYW5lIEdsb25kdQ==?= Cc: caml-list Subject: Re: [Caml-list] Architectures with natdynlink support... References: <4C00303F.8010704@glondu.net> In-Reply-To: <4C00303F.8010704@glondu.net> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam: no; 0.00; frisch:01 frisch:01 makefile:01 dynlink:01 coq:01 ocaml:01 powerpc:01 powerpc:01 -cygwin:01 esac:01 phane:98 0.3:98 10.:98 0.3:98 config:01 On 05/28/2010 11:06 PM, Stéphane Glondu wrote: > Is there a practical test to be sure whether natdynlink works or not? The only way to test if natdynlink works that I know is to try it. In the current trunk, set NATDYNLINK=true in config/Makefile after configure, compile everything, and then run the tests in testsuite/tests/lib-dynlink-native (from testsuite/: "make one DIR=tests/lib-dynlink-native"). Any other application that uses Dynlink in native code is also a sufficient test. > What kind of "feedback" do you expect? Whether natdynlink works or not + the value of $host, $arch64 (and other relevant variables) in the configure script. > As far as Debian is concerned, Coq > dynamically loading ssreflect and compiling stuff works on all native > architectures [2] (as of OCaml 3.11.2), that means: > > - powerpc (powerpc64-unknown-linux-gnu) > - sparc (sparc-unknown-linux-gnu) > - kfreebsd-i386 (i686-unknown-kfreebsd*-gnu) > - kfreebsd-amd64 (x86_64-unknown-kfreebsd*-gnu) > - hurd-i386 (i386-unknown-gnu0.3) > - amd64, i386 (linux kernel) Thanks. The current list is now: case "$host" in *-*-cygwin*) natdynlink=true;; i[3456]86-*-linux*) natdynlink=true;; x86_64-*-linux*) natdynlink=true;; i[3456]86-*-darwin10.*) if test $arch64 == true; then natdynlink=true fi;; powerpc64-*-linux*) natdynlink=true;; sparc-*-linux*) natdynlink=true;; i686-*-kfreebsd*) natdynlink=true;; x86_64-*-kfreebsd*) natdynlink=true;; i386-*-gnu0.3) natdynlink=true;; esac > Maybe people on this list can > also report working natdynlink on other systems. Indeed, this (or any comment on the list above) would be very useful. Regards, Alain