caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Ravi Chamarty <ravi@ittc.ukans.edu>, caml@inria.fr
Subject: Re: Porting OCaml to a Custom OS
Date: Fri, 25 Feb 2000 15:05:34 +0100	[thread overview]
Message-ID: <20000225150534.28706@pauillac.inria.fr> (raw)
In-Reply-To: <Pine.LNX.4.10.10002231549560.5472-100000@george.ittc.ukans.edu>; from Ravi Chamarty on Thu, Feb 24, 2000 at 12:55:13PM -0600

>   I am trying to port ocaml to a custom operating system made using Oskit. I
> have got *ocamlrun* and *ocamlyacc* ported to it. I compiled these on
> Linux 2.2.13 on Redhat 6.0. I forced these tools to be built by using
> 'gcc' with the -nostdinc and -nostdlib so that it only uses the libraries
> and include files I want.  

Sounds good.

>  OSkit presently resides on Linux as a set of libraries and device
> drivers. It has no filesystem .I can boot images of executables which can
> then be loaded as a kernel . 
>   In the case of ocaml, I cannot compile .ml files at this stage since
> they will not run on Linux. How do i force it to compile  .ml files ?

You'll need to cross-compile.  That is, install a regular OCaml on
your Linux development machine and use it to generate bytecode
executables.  Then, hopefully, you should be able to transfer those
bytecode executables to the OSkit memory and execute them from there
using your modified ocamlrun.

- Xavier Leroy



       reply	other threads:[~2000-02-25 17:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.10.10002231549560.5472-100000@george.ittc.ukans.edu>
2000-02-25 14:05 ` Xavier Leroy [this message]
1999-11-24 10:12 OCaml makefile template comments David Mentré
2000-01-09  0:22 ` Porting OCaml to A Custom OS Ravi Chamarty
2000-01-10 13:14   ` Xavier Leroy

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=20000225150534.28706@pauillac.inria.fr \
    --to=xavier.leroy@inria.fr \
    --cc=caml@inria.fr \
    --cc=ravi@ittc.ukans.edu \
    /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).