caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Adrien Nader <adrien@notk.org>
To: Anil Madhavapeddy <anil@recoil.org>
Cc: Xavier Leroy <Xavier.Leroy@inria.fr>,
	Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] [RFC] Remaining changes for cross-compilation support in OCaml
Date: Fri, 21 Feb 2014 08:06:23 +0100	[thread overview]
Message-ID: <20140221070623.GA7924@notk.org> (raw)
In-Reply-To: <B30CB0CD-BD71-4327-84CA-785451A25D15@recoil.org>

On Fri, Feb 21, 2014, Anil Madhavapeddy wrote:
> On 20 Feb 2014, at 16:53, Xavier Leroy <Xavier.Leroy@inria.fr> wrote:
> 
> >> 
> >> **************************** Further Goals ****************************
> >> - cross-compile the compiler: build a native Windows toolchain on Linux
> >> - canadian cross support: ${build}, ${target}, ${host} are all
> >>  different, i.e. on Linux, build a toolchain that runs on Windows 64b
> >>  but targets Windows 32b or a different architecture/OS like ARM Linux.
> > 
> > That could be a nice touch if it's not too much extra work.  The issue
> > was discussed at the last OCaml dev team meeting that Wojciech
> > attended, and we agreed that some scenarios were less important than
> > others, e.g. nobody really needs to compile from a 32-bit host for a
> > 64-bit target.
> 
> This would actually be quite useful for Mirage compilation, since we've
> had quite a few (~10) reports of people attempting to compile up OCaml
> kernels intended for Xen (x86_64) using x86_32 host machines, with one
> brave chap even trying on an ARM32 Chromebook.  The output kernels are
> spun up on a remote cloud service like Amazon or Rackspace, and so being
> flexible about the host machine is helpful.
> 
> (This scenario is certainly less important than the 32-bit target for
> a 64-bit host, but I just thought I'd point it out)

My own use-case is to build Windows binaries of the compiler from Linux
so I can add them to win-builds ( http://win-builds.org ).

I really mention it as a _further_ goal however. I think it could be
achieved without too much work and current changes should keep this
possibility in mind but not try to handle it.
Realistically, the current changes first have to be finished, polished,
checked, released, settled, their bugs fixed...
(well, if the changes are simple, it should be possible to have a set of
"canonical" patches quickly and only merge them later on)

-- 
Adrien Nader

  reply	other threads:[~2014-02-21  7:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18 18:50 Adrien Nader
2014-02-19  9:51 ` [Caml-list] [RFC] Remaining changes for cross-compilation support oleg
2014-02-20 11:03 ` [Caml-list] [RFC] Remaining changes for cross-compilation support in OCaml Goswin von Brederlow
2014-02-21  7:19   ` Adrien Nader
2014-02-20 16:53 ` Xavier Leroy
2014-02-21  0:06   ` Anil Madhavapeddy
2014-02-21  7:06     ` Adrien Nader [this message]
2014-02-21  1:44   ` Francois Berenger
2014-02-21  7:53   ` Adrien Nader
2014-02-21 11:56     ` Benoît Vaugon
2014-02-21 12:52       ` Mark Shinwell
2014-02-22 14:17         ` Adrien Nader
2014-02-22 14:30       ` Adrien Nader
2014-02-22 15:16         ` Gabriel Kerneis
2014-02-22 20:24           ` Richard W.M. Jones

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140221070623.GA7924@notk.org \
    --to=adrien@notk.org \
    --cc=Xavier.Leroy@inria.fr \
    --cc=anil@recoil.org \
    --cc=caml-list@inria.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).