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 mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 276047EEEF for ; Mon, 22 Jun 2015 11:30:28 +0200 (CEST) X-IronPort-AV: E=Sophos;i="5.13,658,1427752800"; d="scan'208";a="166603624" Received: from wencory.loria.fr (HELO [152.81.3.42]) ([152.81.3.42]) by mail2-relais-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES128-SHA; 22 Jun 2015 11:30:27 +0200 Message-ID: <5587D5B3.6080106@glondu.net> Date: Mon, 22 Jun 2015 11:30:27 +0200 From: =?UTF-8?B?U3TDqXBoYW5lIEdsb25kdQ==?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Icedove/31.7.0 MIME-Version: 1.0 To: caml-list@inria.fr CC: Debian Ocaml Maint ML References: <5586835F.9030401@inria.fr> <55868D01.4040603@luminar.eu.org> In-Reply-To: <55868D01.4040603@luminar.eu.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [Caml-list] mips32 backend without floating point hardware Le 21/06/2015 12:08, Vincent Bernardoff a écrit : > I'm using OpenWRT (on a MIPS platform without hardware FP) to develop an > IoT (internet of things) project, and I would like to use OCaml for it. > I don't need floating point in this project but I'd like to be able to > use a "normal" OCaml ecosystem (OPAM, lwt, etc…) that does not work well > in practice without ocamlopt. In Debian, we manage to maintain architectures without ocamlopt (mips, mipsel, ppc64el and s390x at the moment). This is one of the main challenges when packaging for Debian (but it's not that difficult). We also handle the special case of ocamlopt without natdynlink (which was the case of armel for a while). Some upstream packages do it well from the start. For others, a specific Makefile target has to be called when ocamlopt is absent (we try to not patch if possible). Sometimes, upstream sources have to be patched (and we try to forward patches upstream). Any effort to make things better would be greatly appreciated. OPAM packages should be fixed to work without ocamlopt. At the moment, it seems easier to fix packages so that they work without ocamlopt than to port ocamlopt to all architectures (especially if these ports stay unofficial). Moreover, it makes bootstrapping new architectures easier (for example, we had OCaml packages on arm64 as bytecode-only before its support was added in ocamlopt). Cheers, -- Stéphane